[5360] in testers
gconfd errors
daemon@ATHENA.MIT.EDU (Robert A Basch)
Fri May 9 15:28:00 2003
Message-Id: <200305091927.PAA25193@abulia.mit.edu>
To: testers@MIT.EDU
Date: Fri, 09 May 2003 15:27:57 -0400
From: Robert A Basch <rbasch@MIT.EDU>
On both platforms, I see a bunch of gconfd errors syslogged when logging
in an X session. On Linux, /var/log/messages has:
May 9 15:01:25 anhedonia gconfd (systest-12398): starting (version 2.2.0), pid 12398 user 'systest'
May 9 15:01:25 anhedonia gconfd (systest-12403): starting (version 2.2.0), pid 12403 user 'systest'
May 9 15:01:25 anhedonia gconfd (systest-12402): starting (version 2.2.0), pid 12402 user 'systest'
May 9 15:01:25 anhedonia gconfd (systest-12398): Failed to get lock for daemon, exiting: Failed to lock '/tmp/session-systest-12366/gconfd/lock/ior': probably another process has the lock, or your operating system has NFS file locking misconfigured (Resource temporarily unavailable)
May 9 15:01:25 anhedonia gconfd (systest-12403): Failed to get lock for daemon, exiting: Failed to lock '/tmp/session-systest-12366/gconfd/lock/ior': probably another process has the lock, or your operating system has NFS file locking misconfigured (Resource temporarily unavailable)
May 9 15:01:25 anhedonia gconfd (systest-12402): Failed to load source "xml:readonly:/etc/athena/gconf/gconf.xml.mandatory": Failed: Could not make directory `/etc/athena/gconf/gconf.xml.mandatory': Permission denied
May 9 15:01:25 anhedonia gconfd (systest-12402): Resolved address "xml:readwrite:/mit/systest/.gconf" to a writable config source at position 0
May 9 15:01:25 anhedonia gconfd (systest-12402): Resolved address "xml:readonly:/etc/athena/gconf/gconf.xml.defaults" to a read-only config source at position 1
May 9 15:01:25 anhedonia gconfd (systest-12402): Unable to open saved state file '/tmp/session-systest-12366/gconfd/saved_state': No such file or directory
The "starting" and "Resolved" messages are informational, but the rest are
problems. The multiple "starting" and "failed to get lock" messages suggest
a race condition, caused by clients simultaneously trying to start the
daemon. Perhaps a strategically placed "gconftool-2 --spawn" command
in /usr/athena/lib/init/xsession will solve this nicely.
The complaint about /etc/athena/gconf/gconf.xml.mandatory seems like a
package install problem (the directory does not exist).
The complaint about the "saved state file" is expected in our environment,
since the gconfd directory is unique per session. I will submit a patch
to change this message to debug level.
