GNOME Bugzilla – Bug 126468
gconf should not spam the syslog
Last modified: 2008-05-07 10:23:25 UTC
This bug was originally reported in the Debian BTS: http://bugs.debian.org/188433 "gconfd, when running for normal users, constantly spams the syslog like so: Apr 10 18:49:29 continuity gconfd (luke-30413): Resolved address "xml:readonly:/etc/gconf/gconf.xml.mandatory" to a read-only config source at position 0 Apr 10 18:49:29 continuity gconfd (luke-30413): Resolved address "xml:readwrite:/home/luke/.gconf" to a writable config source at position 1 Apr 10 18:49:29 continuity gconfd (luke-30413): Resolved address "xml:readonly:/etc/gconf/gconf.xml.defaults" to a read-only config source at position 2 On a multiuser system, this really adds way too much noise to the signal. By default gconfd should not log here."
From http://www.gnome.org/projects/gconf/plans.html: Get rid of syslog stuff, or at least only syslog for genuine serious errors. I think while we're at this, we should take a look at making it easier to debug gconfd-2, maybe with a logfile like the metacity one.
It seems this got lost on your current "GConf Future Improvements" list?
Created attachment 85220 [details] [review] Downgrade log priority to DEBUG for these messages Here's a proposed patch with David Förster sent in Debian bug http://bugs.debian.org/188433.
Created attachment 110376 [details] [review] debian patch Debian are actually using a somewhat more radical patch for de-syslogification. I've added this patch to our Fedora packages now. We should probably merge it upstream.
*** Bug 526680 has been marked as a duplicate of this bug. ***
I commited this now.