[OpenAFS] gconf lock problem

Derrick J Brashear shadow@dementia.org
Wed, 13 Apr 2005 18:44:27 -0400 (EDT)


On Wed, 13 Apr 2005, chas williams - CONTRACTOR wrote:

> it might be fixed in the 1.3 series.  i did some work to try
> to make this problem go away.  it would be nice if you could
> try the 1.3 series and let us know if it appears to solve
> your problem.

Hm. I didn't think to test 1.3. Anyhow, it's a weird combination of how 
the gconf lock is handled (hard links involved) and a server restart at 
the "wrong" time.

Salvaging the volume individually will also fix the problem.

Or you could do what happens as default in gnome 2.4 anyway:
setenv GCONF_LOCAL_LOCKS 1

and it will use /tmp as lock dir.