[OpenAFS] gconf lock problem

[Mike McCabe]

Renata
The quick fix if your using pam for authentication is to edit your pam 
configuration file for gdm or login (depending on how you have it set 
up) Here's the the line that we had to add to get ride of that issue.  
The remainlifetime gives enough time for the files to close.  You can 
just delete the files if the user's currently having a problem though. 
We also have a script that removes /tmp/gconf-d* and /tmp/orbit* that 
runs in cron.

session    sufficient   /lib/security/pam_afs.so ignore_root 
remainlifetime 15

Mike

Renata Maria Dart wrote:

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