Re: Gconf deadlock at startup

[Frederic Crozat <fcrozat mandrakesoft com>]

le mer 28-11-2001 à 19:54, Havoc Pennington a écrit :
> 
> Frederic Crozat <fcrozat mandrakesoft com> writes:
> > Just got a very annoying problem with GConf 1.0.7 but I don't know how
> > we could fix it cleanly..
> > 
> > -run a GConf-enabled application with a NFSv3 (with lockd running) (in
> > my example, Nautilus and Evolution with gconf support in gtkhtml)
> > -turn off the computer (well, I found my computer off without any good
> > reason)
> > -turn on and try to launch Evolution (or Nautilus) => GConf isn't able
> > to launch correctly..
> > 
> > Since there is no error popup nor on console (but only in
> > /var/log/message), (newbie) user doesn't know what is the problem..
> > 
> > After digging in /var/log/message, I found :
> > Failed to get lock for daemon, exiting: Failed to lock
> > '/home/mandrakesoft/fcrozat/.gconfd/lock/ior': another process has the
> > lock (Resource temporarily unavailable)
> > 
> > Lock is still kept (in gconf-internal(open_empty_locked_file)) even if
> > there is no longer any gconfd deamon running..
> 
> I don't understand the issue - you turned off the NFS server or the
> NFS client? It sounds like this is simply an NFS limitation... 

Well, nfs client was turned off when my computer power got turned off
...

> GConf just relies on file locking working... if it doesn't, there's
> not much we can do about it.

Yep, I agree. I'm wondering if we can a clean way to prevent this kind
of deadlock.. (because NFS mounted home are used a lot..)

-- 
Frédéric Crozat
MandrakeSoft