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.
I have been following this NFS Server How-To, and I have run into problem. I am not sure how to set up the startup scripts such that all the correct daemons are running as shown here:
Quote:
3.3.3. The Daemons
NFS serving is taken care of by five daemons: rpc.nfsd, which does most of the work; rpc.lockd and rpc.statd, which handle file locking; rpc.mountd, which handles the initial mount requests, and rpc.rquotad, which handles user file quotas on exported volumes. Starting with 2.2.18, lockd is called by nfsd upon demand, so you do not need to worry about starting it yourself. statd will need to be started separately. Most recent Linux distributions will have startup scripts for these daemons.
The daemons are all part of the nfs-utils package, and may be either in the /sbin directory or the /usr/sbin directory.
If your distribution does not include them in the startup scripts, then then you should add them, configured to start in the following order:
rpc.portmap
rpc.mountd, rpc.nfsd
rpc.statd, rpc.lockd (if necessary), and rpc.rquotad
Do anyone have some suggests or a startup script FAQ that they an point me to?
Thank you for your response. I have those running via those same commands. My trouble is getting the others started as are listed here:
Quote:
If your distribution does not include them in the startup scripts, then then you should add them, configured to start in the following order:
rpc.portmap
rpc.mountd, rpc.nfsd
rpc.statd, rpc.lockd (if necessary), and rpc.rquotad
When I run the same commands with the above scripts, I receive an error to the effect of service not found. I do have the scripts: some are located in /sbin and others in /usr/sbin. Will I have to do a sym link from their current location to /etc/init.d (or wherever the scripts reside, I'm not at my linux machine) or can I use the chkconfig and service commands such that "chkconfig /sbin/rpc.portmap on."
Also, how does one order services? Just edit the conf file? This all is pretty new to me, so I don't want to tinker too much.
Seems like its all running, but I keep getting the following error: "NFS Portmap: RPC: Port mapper failure - RPC: Timed out." The NFS Server is FC3, and the NFS client is Mac OS 10.3.8.
Edited to Add: I had one of the two NFS ports closed, so after opening them I got the following error: "mount_nfs: bad MNT RPC: RPC: Timed out."
2) save and quit
then run the command eportfs -rav
You should get a list of your exports.
3) now restart the service as stated above in an earlier post.
If that fails have you lokked in hosts.allow and hosts.deny?
Or try flushing your firewall iptables -F
I sugesst you comment out all the lines in hosts.allow and hosts.deny.
Then iptables -F followed by service iptables stop
Make sure that you can rpcinfo -p <nfs server> from another host on the network.
If thats ok try showmount - e <server name> from another host.
Then try the mount command from above.
Okay, I had a bit of breakthrough. With "ALL:ALL" commented in hosts.deny and everything as I listed before in hosts:allow, my NFS client worked! (To those of you trying to use your OS X machine as a host, you will have to add the "insecure" option to the directory you wish to share in your exports file as per this site.) On my NFS client, an app called nfs_mount seems to depend upon three ports: 672, 675, and 685. I'm not sure if this unique to OS X or common to all NFS clients, but I kept seeing it bounce off my firewall during my attempts to connect to the server.
Enter the "but." When I can connect to my /home directory, I do not have permission to access two of the three user directories. I'm worried my permissions are screwed up somehow--the inconsistency is what bugs me. Any thoughts?
Thanks for all the input, great info!
Last edited by General_Tso; 03-20-2005 at 12:10 AM.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.