https://qa.mandrakesoft.com/show_bug.cgi?id=305
[EMAIL PROTECTED] changed:
What |Removed |Added
----------------------------------------------------------------------------
AssignedTo|1935 |5
Status|NEW |RESOLVED
Resolution| |INVALID
------- Additional Comments From [EMAIL PROTECTED] 2003-01-15 14:00 -------
sorry but it's look likeyou have problem somewhere else, default rpm
has clearly :
chmou@no|~| rpm -qpl -v /RPMS/nfs-utils-clients-1.0.1-1mdk.i586.rpm
[...]
drwx------ 2 rpcuser rpcuser 0 Aug 1 22:10 /var/lib/nfs/statd
and on a default cooker installation i have :
(root@valorum)[nfs]-$ ls -ld statd/
drwx------ 4 rpcuser rpcuser 4096 jan 6 15:42 statd/
(root@valorum)[nfs]-$
and rpc.statd doen't have any problems.
------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.
------- Reminder: -------
assigned_to: [EMAIL PROTECTED]
description:
The rpc.statd daemon fails to start correctly on 9.0rc1 becuase the directory
structure under /var/lib/nfs/statd is owned by user 'root'. Instead, the files
should be owned by user 'rpcuser'.
Altering the file/directory permissions fixes the problem:
chown -R rpcuser.rpcuser /var/lib/nfs/statd/
The problem will manifest itself when a user tries to initiate a Gnome login
session where the /home directories are mounted over NFS. By default, gconf will
attempt to obtain an NFS lock in the user's home directory using a file named
'/home/user/.gconf-test-locking-file'. Because rpc.statd was not started
correctly by the /etc/init.d/nfslock startup script, this attempt to obtain a
NFS lock will fail, and the user will not be able to log into the Gnome desktop.
-jason
