Linux - SoftwareThis forum is for Software issues.
Having a problem installing a new program? Want to know which application is best for the job? Post your question in this forum.
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.
You get the error - stopping NFS statd FAILED - because a kill signal is sent to all services including the NFS service when shutting down the system. However, since NFS is not running, it fails to stop the service and hence shows the error message.
To check if NFS is running or not, just give the following command logged in as root
You would be aware that there are the following runlevels in linux
0 - Shutdown
1 - Single User Mode
2 - Multi User without NFS
3 - Multi User with NFS
4 - Unused
5 - X-Window (GUI)
6 - Reboot
Now, there are services which are started at the time of boot. All these scripts reside in
Further, every run level has some specific services running. So lets suppose that if you switch your run level from 3 to 5, there will be some services that will be started when you enter runlevel 5 , and some services that wll be stopped when you enter runlevel 5.
each of these run-levels has a corresponding directory
/etc/rc.d/rc0.d for runlevel 0
/etc/rc.d/rc1.d for runlevel 1
/etc/rc.d/rc2.d for runlevel 2
/etc/rc.d/rc3.d for runlevel 3
/etc/rc.d/rc4.d for runlevel 4
/etc/rc.d/rc5.d for runlevel 5
/etc/rc.d/rc6.d for runlevel 6
Whenever you boot in a particular run level, scripts in its corresponding directory are executed. The files in rcX.d directories are basically links to the scripts in the directory /etc/rc.d/init.d/
Thus, a file beginning with an 'S' means that a particular service will be started...whereas a file name beginning with 'K' means the service will be killed in that particular run-level.
Skudzu - means start the kudzu service
Knfsd - means kill the NFS service
So in every run level, some services will be killed and some new services will be started, and the remaining that are common to both runlevels will keep running.
You should have a look at the above directories for more information.
ya you can turn it off, and that will aliviate your error. In the redhat menu, I think their is somthing called network services. you need to uncheck nfslock, the stopping NFS statd FAILED error will go away.