[OpenAFS] gconf lock problem

[Michael Wimpee]

We had this problem with 1.2.11 and resolved it by making gnome store 
the lock files locally:

/etc/profile.d/gnome.csh:
setenv GCONF_LOCAL_LOCKS 1

/etc/profile.d/gnome.sh:
if [ -n "$BASH_VERSION" -o -n "$KSH_VERSION" -o -n "$ZSH_VERSION" ]; then
  # for bash, pdksh and zsh
  export GCONF_LOCAL_LOCKS=1
fi

While the settings are still stored in ~/.gconf, the locks are stored in 
/tmp/gconfd-[username]/.

Mike Wimpee

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