Re: gnome (gconf) saga - please read

["Timothy H. Keitt" <tklistaddr keittlab bio sunysb edu>]

On Sun, 2002-03-03 at 21:14, Havoc Pennington wrote:
> 
> GConf has no more information than the kernel does - if the kernel
> says the file is locked, GConf has no basis to second-guess.  If it
> did try to second guess, then it would make mistakes.  And that leads
> to silent config corruption, rather than the obvious "config doesn't
> work" situation that happens now.
>   
> So I think the best we can do is ask the user to intervene manually,
> and fix the OS bug.
> 

Perhaps you could have gconf periodically renew its locks; any locks
older than the refresh interval could then safely be removed.

T.