Re: Lock problem

[Havoc Pennington <hp redhat com>]

"Adam D. Gorski" <agorski engin umich edu> writes:
> Mar 23 17:25:49 Zaphod gconfd (agorski-45615): Failed to give up lock on XML
> dir `/home/agorski/.gconf': Failed to link
> '/home/agorski/.gconf/%gconf-xml-backend.lock/2t1016925949ut223485u1000p45615r2072237912k3217028248'
> to '/home/agorski/.gconf/%gconf-xml-backend.lock/ior': No such file or
> directory
... 
> 
> I'm not really sure what to make of this, and I don't know how to fix it.
> Gconf got installed via ports when I installed some software, and usually
> ports are pretty stable and well-configured. If you guys have any ideas and
> or suggestions, I would love to hear them. Thanks!
> 

I'm not sure what's going on.  What's failing is gconfd trying to
clean up a lock file, but if the cleanup fails the damage is just that
you have an old file laying around, it doesn't break anything.

If you want the big picture, I have a shiny new web page:
 http://www.gnome.org/projects/gconf/
that might give you some ideas.

What kind of worries me about your warning is that the gconfd
apparently thinks it has a lock on .gconf/%gconf-xml-backend.lock/ior,
but .gconf/%gconf-xml-backend.lock/ior does not exist? That could
cause problems.

I haven't seen this warning before, so am interested in what it might
be.

Havoc