gconfd noise in system logs

["Phil Edwards" <phil m edwards gmail com>]

We're running FC7, using gnome-python2-gconf-2.18.1-1.fc7.  I'm getting
a metric crapload of

gconfd (<user>-8186): starting (version 2.18.0.1), pid 8186 user '<user>'
gconfd (<user>-8186): Resolved address
"xml:readonly:/etc/gconf/gconf.xml.mandatory" to a read-only
configuration source at position 0
gconfd (<user>-8186): Resolved address
"xml:readwrite:/home/<user>/.gconf" to a writable configuration source
at position 1
gconfd (<user>-8186): Resolved address
"xml:readonly:/etc/gconf/gconf.xml.defaults" to a read-only
configuration source at position 2
......
gconfd (<user>-8186): GConf server is not in use, shutting down.
gconfd (<user>-8186): Exiting

in my system logs, pretty much every time a user logs in to any of the
consoles.

I don't need a permanent record of every time gconf starts up, exits,
or where it found the exact same files as it found them from five minutes
earlier.  ><  But I don't know what syslog severity it's using, or where
gconfd's syslog settings are stored.  I'd love to turn this noise off
completely, but as a fallback I can just tell it to use some spare syslog
facility (e.g., local5) instead of the general facilities.

Then local5 messages can all be discarded, or at least set in syslog.conf
to a higher threshold than "every startup and exit event".

I couldn't find any such settings under /etc/gconf, but I know very little
about how gconf works.  Any help would be appreciated.