Hi Matt, On 4/17/19 1:08 AM, Matt Benjamin wrote:
Why is using an explicit unix socket problematic for you? For what it does, that decision has always seemed sensible.
In fact, I don't understand why the "ops" logs have a different way from the logs of the process radosgw itself. Personally, if radosgw is launched without a foreground option, it seems to me logical that "ops" logs are put in "log_file" (ie /var/log/ceph/$cluster-$name.log by default) and if radosgw is launched with a foreground option (ie -d or -f) it seems to me logical that "ops" logs are put in stdout/stderr too. Is there a specific reason to put "ops" logs in a different location from the logs of the process radosgw itself? "ops" logs are logs of the "radosgw" process, no? In my case, I use ceph-ansible with docker containers (it works fine by the way ;)): 1. a systemd unit launches a docker container 2. the docker container launches a radosgw process with the -d option (ie "run in foreground, log to stderr"). 3. systemd logs stdout/stderr of the process radosgw in syslog. It could be handy for me if "ops" logs were directly put in stderr/stdout. No? -- François (flaf) _______________________________________________ ceph-users mailing list ceph-users@xxxxxxxxxxxxxx http://lists.ceph.com/listinfo.cgi/ceph-users-ceph.com
