SlackwareThis Forum is for the discussion of Slackware Linux.
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.
I've read all the NFS threads that have been popping up lately and none of them seem to help me resolve my current "issues". I tried following this tutorial here at LQ and the documentation on the NFS page and I'm still having problems. I got the server end working no problem with a basic installation from the Slack 10.2 discs I made a few weeks back. This is what I get on the server box with rpcinfo -p
Which should be good to go no? On my main box that I'm using as the client (I'm only sending files from my main box to the server box since its my webserver experiment so there is no server running on this end) I get:
Code:
program vers proto port
100000 2 tcp 111 portmapper
100000 2 udp 111 portmapper
I installed Slack on both boxes from the same discs and the only thing I didn't install on my main box (the one that's not working) was the Apache stuff. Doing an slocate on --> nfsd, lockd, statd, mountd, and rquotad returns nothing.
What are the "issues"?
Did you export any directories on the server?
Did you mount it from the client?
Any error-messages? In the system-logs...? slocate only works if you ran "updatedb" - and it would only give the location of the file - it doesn't say anything about if a service is running or not - but portmap running on the client would be enough.
Hehe .. sorry .. guess I gave all the background and not my problem. I couldn't find any of the services daemons anywhere on my computer, so that's what I was using slocate for, and I do keep it updated by running updatedb at least once a day. I found the portmap daemon and the portmap service is running on the box on startup, I just can't find any of the other ones the NFS site says I need. When I try to mount the other computer with:
Code:
mount -t nfs 192.168.1.101:/var/www /mnt/oldSlacky
/etc/export on the server box looks like this (192.168.1.100 is the IP of my main box -- the one that won't connect)
Code:
# See exports(5) for a description.
# This file contains a list of all directories exported to other computers.
# It is used by rpc.nfsd and rpc.mountd.
/var/www 192.168.1.100(rw)
# End of Exports file
Sorry for the mess of code, but I thought that'd help more than me trying to describe the problem. I guess what has me confused is that I installed Slack on both from the same CDs and I've actually pruned down the server box since it's just a webserver on a really old box and finding those daemons and starting those services was a piece of cake.
So far it seems you have setup everything correctly. I had an access denied problem once with rpc and flushing the iptables solved it. In your case...hmmm I'm looking.
where directory [is] the directory that you want to share. It may be an entire volume though it need not be. If you share a directory, then all directories under it within the same file system will be shared as well.
machine1 and machine2 [are] client machines that will have access to the directory. The machines may be listed by their DNS address or their IP address (e.g., machine.company.com or 192.168.0.8). Using IP addresses is more reliable and more secure. If you need to use DNS addresses, and they do not seem to be resolving to the right machine, see Section 7.3.
And changing it to the IP of the server didn't fix it either. The only service that's running on the client is the portmap daemon. Is that really all I need to have running? The NFS page said there were 3 services I needed running in addition to portmap.
hmm well the last time I set it up, portmap and nfs were the only related daemons I had running on the client side. So you probably need nfs
Where can I get that? I downloaded the latest nfs-utils tarball from the NFS site and after having to track down and intall three different dependencies I got the feeling I was doing something wrong. I still don't understand why it was so easy to get the server services running without any dependency or any of the other issues I'm having with the client.
Try allowing to your whole net instead of just one IP.
I tried that and it didn't work.
I just installed the nfs-utils from my Slack discs and I still get the same error message when I try to mount it on the client side. Here is the output of ps aux from the client logged in as root right after a reboot.
rpc.lockd, rpc.statd, rpc.mountd, and rpc.portmap are all -rwxr-xrwx in the /usr/sbin directory so according to the NFS site I should be good to go, right?
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
I tried following 
I couldn't find any of the services daemons anywhere on my computer, so that's what I was using slocate for, and I do keep it updated by running updatedb at least once a day. I found the portmap daemon and the portmap service is running on the box on startup, I just can't find any of the other ones the NFS site says I need. 
