[OpenAFS] gconf lock problem

chas williams - CONTRACTOR chas@cmf.nrl.navy.mil
Wed, 13 Apr 2005 18:38:27 -0400


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.

In message <200504132215.j3DMF5eO005517@mailbox.slac.stanford.edu>,Renata Maria
 Dart writes:
>Hi, is the gconf lock problem fixed in some version of
>OpenAFS?  This is the problem whereby a gconf user finds that
>they cannot login because of a corrupt .gconfd/lock and/or a
>corrupt /.gconf/%gconf-xml-backend.lock, and the only fix is
>to rename them?  I recently installed 1.2.13 on all of our 
>servers and I just got a report of another user experiencing 
>the problem.
>
>Thanks,
>
>Renata
>
>
> Renata Dart                         | renata@SLAC.Stanford.edu  
> Stanford Linear Accelerator Center  |    
> 2575 Sand Hill Road, MS 97          | (650) 926-2848 (office)
> Stanford, California   94025        | (650) 926-3329 (fax)
>
>
>_______________________________________________
>OpenAFS-info mailing list
>OpenAFS-info@openafs.org
>https://lists.openafs.org/mailman/listinfo/openafs-info
>