Why is gconfd starting twice?

[Frank McCormick]

On Mon, 28 Aug 2006 20:20:52 +0100
Adam Funk <a24061 at yahoo.com> wrote:

> On 2006-08-27, Adam Funk <a24061 at yahoo.com> wrote:
> 
> >>   gconfd (adam-2543): Failed to get lock for daemon, exiting: Failed
> >>   to lock '/tmp/gconfd-adam/lock/ior': probably another process has
> >>   the lock, or your operating system has NFS file locking
> >>   misconfigured (Resource temporarily unavailable)
> >>
> >> in my logcheck output from every X login and figured out that for some
> >> reason gconfd is trying to start twice every time I log in:
> > ...
> >> Any suggestions on debugging it?  
> >>
> >> Or should I just ignore it?
> >
> > I don't know why, but installing the gconf package (in addition to
> > gconf2, which I already had) has made this error go away!
> 
> No it hasn't.  It just didn't happen for a day after I installed
> gconf; now it's back.  Any ideas?
> 


This has been going on on my machine since I don't know when - probably since I switched to Dapper. But it doesn't seem to affect anything.



(extract from user.log)

Aug 28 20:39:33 localhost gconfd (frank-4094): starting (version 2.14.0), pid 4094 user 'frank'
Aug 28 20:39:33 localhost gconfd (frank-4092): starting (version 2.14.0), pid 4092 user 'frank'
Aug 28 20:39:33 localhost gconfd (frank-4092): Failed to get lock for daemon; exiting: Failed to lock '/tmp/gconfd-frank/lock/ior': probably another process has the lock, or your operating system has NFS file locking misconfigured (Resource temporarily unavailable)
Aug 28 20:39:33 localhost gconfd (frank-4090): starting (version 2.14.0), pid 4090 user 'frank'
Aug 28 20:39:33 localhost gconfd (frank-4090): Failed to get lock for daemon; exiting: Failed to lock '/tmp/gconfd-frank/lock/ior': probably another process has the lock, or your operating system has NFS file locking misconfigured (Resource temporarily unavailable)
Aug 28 20:39:34 localhost gconfd (frank-4094): Resolved address "xml:readonly:/etc/gconf/gconf.xml.mandatory" to a read-only configuration source at position 0




-- 
Cheers

Frank