Linux - NetworkingThis forum is for any issue related to networks or networking.
Routing, network cards, OSI, etc. Anything is fair game.
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Introduction to Linux - A Hands on Guide
This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter.
For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own.
Click Here to receive this Complete Guide absolutely free.
I have a very strange problem. My NFS server is FC3, my NFS client is RH9. On the client i get the log message:
kernel: lockd: cannot monitor <IP of the server>
kernel: lockd: failed to monitor <IP of the server>
after somne googling, I found that the problem was in rpc.statd that should be activated by nfslock startup script. nfslock is enabled (chkconfig shows it "on") and calls "rcp.statd". When I execute rcp.statd, it dies right away: it does not appear in ps.
I work on a cluster on which all the nodes have / mounted on NFS on onather server and they have write permissions only to /tmp /var and /etc but this should not be the problem since I do not get any permission denied error when I execute rpc.statd, even strace rpc.statd does not show any problems of permission.
On the server I get another message that may have something to do with the aforementionned issue:
Received erroneous SM_UNMON request from <name of the NFS server> for <name of the client>
the funny part is that the specific client that appears is this log message is a normal RH9 (/ is not mounted on NFS) and on this client rpc.statd runs...