Re: Lock problem

["Adam D. Gorski" <agorski engin umich edu>]

If I understood you correctly:

agorski Zaphod:~/.gconf/%gconf-xml-backend.lock $ls -l
total 2
-rwx------  1 agorski  agorski  266 Mar 24 11:47 ior

Is that the file? It's there :(

Also, the file contains a huge string starting with:

46815:IOR:010000001500000049444c3a436f6e66 etc.


I'm willing to work with you guys on this, and I can provide as much
info/testing/etc as needed. I figure I can help you out maybe, and you can
help me out for sure :)

- Adam

On 24 Mar 2002, Havoc Pennington wrote:

::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
::