Hi Colin, On 2011. August 16. 06:10:32 Colin McCabe wrote: > 2011/8/15 Colin McCabe <cmccabe@xxxxxxxxxxxxxx>: > > 2011/8/15 Székelyi Szabolcs <szekelyi@xxxxxxx>: > >> Hi all, > >> > >> I'm running a Ceph cluster with a number of read-only ramdisk based > >> clients mounting the filesystem. I'd like to get the logs of the client > >> out via syslog. I've seen some posts dealing with logging to syslog, > >> namely the thread starting at > >> http://www.spinics.net/lists/ceph-devel/msg02876.html . I see options > >> like "log to syslog" and "clog to syslog". It's not clear what they > >> mean, could someone tell me the difference? > > > > "clog" is the center logger, which is a separate subsystem from the > > regular logger. The central log is maintained by the monitors rather > > than being a per-daemon thing like the regular log. My would have gone to clog = client log. Thanks for the clarification. > >> Anyway, currently my logging settings on the client are > >> > >> [global] > >> log file = > >> log dir = > >> log to syslog = true > >> clog to syslog = true > >> > >> But when the filesystem is mounted with the FUSE client, I still get > >> > >> failed to open log file '/var/log/ceph/client.admin.log': error 2: No > >> such file or directory > >> > >> which is surprising. I thought that the above options should have > >> disabled logging to file, but it looks like it still tries to open it. > >> Is this a bug, or me doing something wrong? > > > > This looks like an actual bug :( > > I'm testing out a fix that will allow users to turn off log files for > > daemons again. > > This should be fixed in master by > 8072bdcaa4445359051fed443be3d702f20807e0 > > This should fix it for you. Thanks, Colin. Since I don't compile sources myself, I'll wait for the next release to roll this out. -- cc -- To unsubscribe from this list: send the line "unsubscribe ceph-devel" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
