|
Home > Archive > Unix administration > September 2007 > authentication, nfsd, and home directories
You are viewing an archived Text-only version of the thread.
To view this thread in it's original format and/or if you want to reply to
this thread please [click here]
| Author |
authentication, nfsd, and home directories
|
|
| Marc Girod 2007-09-05, 7:26 am |
| Hello,
Some users on my site cannot login to some linux boxes, on the
console.
In one case, we get the following error (popup, on the X console):
Could not lock the file "/home/kkegl/.gconf-test-lockingfile";
This indicates that there may be a problem with your operating
system configuration. If you have an NFS mounted home
directory, either the client or the server may be set up
incorrectly. See the rpc.statd or rpc.lockd documentation.
A common cause of this error is that nfs lock server has been
disabled. The error was "permission denied" [errno=13]
Indeed, the mention of the host serving the home directories
seems to hit a nail on the head: the users who can login use
a different one (Solaris 8) than the ones who cannot (Solaris 6).
This is not an exhaustive survey, though: only a few users.
Trying to compare the rpc services registered on both servers,
with the folowing command (run from a Solaris box):
rpcinfo <host> | awk '{print $5}' | sort -u
I do find that (among others) the two following daemons are
running on the Solaris 8 box (home of working cases) but not
on the Solaris 6 one: rstatd and nlockmgr.
I am not administering the Solaris 6 box, and have a hard
time convincing the administrator that something may be
wrong ("has been working for the last 9 years").
So, could I get some advice?
- Am I on the right track?
- I could of course stop the two daemons on the Solaris 8
box to check whether this affects, but this might have
undesirable side-effects... or might it?
Thanks!
Marc
|
|
|
|
|