After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 106867 - NFS Locking problem in HOME
NFS Locking problem in HOME
Status: RESOLVED DUPLICATE of bug 84101
Product: GConf
Classification: Deprecated
Component: gconf
CVS HEAD
Other Linux
: Normal major
: ---
Assigned To: GConf Maintainers
GConf Maintainers
Depends on:
Blocks:
 
 
Reported: 2003-02-23 17:30 UTC by Andrew Hamilton-Wright
Modified: 2004-12-22 21:47 UTC
See Also:
GNOME target: ---
GNOME version: 2.0



Description Andrew Hamilton-Wright 2003-02-23 17:30:32 UTC
If gconf cannot put a lock in $HOME, then the desktop is not started.

This is a problem when the $HOME directory is NFS mounted from a different
client which does not run statd/lockd.  The lock daemons have had a number
of security and other issues, so running them is not necessarily desired;
even if run, version issues frequently prevent them from working correctly.

An option to Gnome to avoid locking (assuming only one login/user at a
time) would solve the problem.

Currently we cannot use the more recent release (through RedHat) of Gnome,
as it will refuse to lay out a (single) desktop.
Comment 1 Havoc Pennington 2003-02-23 17:32:19 UTC
See http://www.gnome.org/projects/gconf/ which discusses the issue in
some detail and mentions the GCONF_LOCAL_LOCKS=1 workaround.
Comment 2 Havoc Pennington 2003-03-06 05:07:46 UTC

*** This bug has been marked as a duplicate of 84101 ***