FedoraThis forum is for the discussion of the Fedora Project.
Notices
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.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Under slackware you can try commenting the `locked' line in
/etc/hosts.allow and /etc/hosts.deny. That might help. But
if you start-up scripts are calling the NFS daemon, then you
might need this line. If you are sharing files from that PC I suggest
you read this and particularly this
Under KDE, if you go to the main menu, System Settings->Server Settings->Services (or type system-config-services at a prompt as root), you can disable NFS locking. I don't know exactly what it is, but it relates to the network file system (NFS), so if you aren't using that you don't need it.
In the Service Configuration window that comes up, just untick the box that says nfslock in the left window and click save. You might also want to do this for runlevel 3.
I did the same thing by going to the services and deselecting nfslock. Then I shut down the system. The error " Stopping NFS Locking failed" still come up. This error doesn't affect you to start up or shut down your Linux system. But the red error sign make me uphappy with the system. Who can provide more info and ways to fix it?
NFS is the network file system, and it is used to remotely access disk space. For instance, I use NFS in the computer lab that I administer. We have one file server which allows all the other computers to mount the "/home" directory, where all my users put their mission critical data.
If you are not using NFS, you can just disable all NFS services, something like
Code:
chkconfig --level 2345 nfs off
chkconfig --level 2345 nfslock off
Starting with the next time you boot your computer, you shouldn't see notices about the NFS service any more.
Thanks for your input. I have read some of the threads that gave me different approaches to fix this problem such as check /etc/init.d/nfslock to see what it does, Or go to /etc/rc5.d to rm S57netfs, K57netfs, S20nfs, K20nfs, S86nfslock, K86nfslock, or do chkconfig --del nfs. I also read some papers how to config NFS on server and client.
My current system with FC4 is a testing server. There is no any client will access and mount file system on it. I have checked /etc/rc5.d/, I even do not have S57netfs, K57netfs, S20nfs, S86nfslock, K86nfslock files. But I do have K20nfs over there. When I boot system, I can see that starting NFS stated OK. Does this mean that NFS locking has been started whth the system booting? Why can not system automatically stopping NFS locking? I do think your way might work for this problem. I just want to make sure this is at least the better way than others. Please give me more tips on this. Thanks a lot.
All of those approaches that you list are variants of the cleaner method I gave you, the method of using "chkconfig --level". If you look in /etc/rc.d/rc5.d, you will notice all the elements starting with "S" or "K" are links to things in /etc/init.d. The "S" means these services will be started. The "K" means these services will be killed (or not started).
For whatever reason, NFS services are spread amongst netfs, nfs, and nfslock. I don't know why they're split that way, but I'm sure there's a good reason. If you don't need any of them (which it sounds like you don't), then just do a
Code:
chkconfig --level 2345 netfs off
chkconfig --level 2345 nfs off
chkconfig --level 2345 nfslock off
It will just create "K"-type entries in your /etc/rc.d/rcX.d directories, and you won't have to worry about those services starting up during boot.
This page will help understand the "why" about this.
Unless you operate NFS and NFSLOCKING in all those boot levels, there is no need to worry about them. Read this page and it will explain in easy to understand English what each of the services are for and whether you need them or not.
Even though this is for Fedora-8 it holds true for Fedora-4 as well and there are links to other things there that I am sure you will find interesting.
HTH,
George
Last edited by chipha; 11-16-2007 at 11:20 AM.
Reason: to make more clear
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.