Gnome freezen up with NFS /home
About two weeks ago I installed stable, with unstable OpenOffice, on a
user system with security updates. The user, alples, has an NFS /home
directery mounted from a Sun I don't have root access to.
In the began the nfs /home directory mounted: soft,bg,rw
but when she logged in Gnome would freeze up and the log would get:
Nov 14 14:41:56 trade gconfd (alples-637): Failed to get lock for daemon,
exiting: Failed to lock '/ac/res/cs9/alples/.gconfd/lock/ior': probably
another process has th
e lock, or your operating system has NFS file locking misconfigured, or a
hard NFS client crash caused a stale lock (No locks available)
Nov 14 14:41:56 trade gconfd (alples-639): starting (version 1.0.9), pid
639 user 'alples'
Nov 14 14:41:56 trade kernel: lockd: cannot monitor 138.15.x.y
Nov 14 14:41:56 trade kernel: lockd: failed to monitor 138.15.x.y
as she never logs into other systems I added the nolock option and all
want well from a week. The /proc/mounts has the following options on
/home partitions:
rw,v3,rsize=32768,wsize=32768,soft,udp,nolock,addr=xy.nj.nec.com
Today gnome freezes up again with the following
running:
$ ps -fu alples
UID PID PPID C STIME TTY TIME CMD
alples 506 456 0 10:35 ? 00:00:00 /usr/bin/gnome-session
--purge-delay=15000
alples 532 506 0 10:35 ? 00:00:00 /usr/bin/ssh-agent --
/usr/bin/gnome-session --purge-delay=15000
alples 536 1 0 10:35 ? 00:00:00 gnome-smproxy
--sm-config-prefix /.gnome-smproxy-TZAlon/ --sm-client-id
118a0fa88e000103737388900000004700000
alples 548 1 0 10:35 ? 00:00:00 sawfish --sm-client-id
118a0fa88e000103737389300000004700003 --sm-prefix a7vro0b87l
no system errors this time. I got it to work again by deleting .gnome*
files and friends but I don't think that is a long term solution.
She used to use Mandrake 8.x on her desktop with /home from nfs and I
never had this problem.
Sven
Reply to: