The most likely problem is that your /etc/exports file has a hidden control character somewhere in it, which is messing things up. Try deleting the entire file and retyping it in. The same /etc/exports as your email works for me, so it isn't a problem with how you've set it up. Ewan On Sat, 2002-07-20 at 18:42, Chris Carlen wrote:
Hi: (Suse 7.3)
I have a server machine named tong 192.168.0.12 which has /etc/exports:
/ 192.168.0.0/255.255.255.0(ro) /home 192.168.0.0/255.255.255.0(rw)
And on the client machine ting 192.168.0.11 I can mount the tong:/home , but I can't mount tong:/
Also, tong gives an error when I run the nfsserver:
tong:/ # /etc/init.d/nfsserver restart Shutting down kernel based NFS server done Starting kernel based NFS server192.168.0.11:/: Invalid argument done
Why does the nfsserver script mention ting's IP when trying to restart?
If I take out the line attempting to export / in tong:/etc/exports, then the nfsserver script doesn't give an error.
Now what's really strange is that we can reverse the situation:
Ting also runs nfsserver, and has the exact same /etc/exports . However, tong can mount ting:/ with no problem! For the life of me I cannot find a difference in the connfigurations of the two machine's NFS setups. Hosts.deny/allow are the same as well.
Digging a little deeper, I find that when I run on tong:
tong:~ # exportfs 192.168.0.0/255.255.255.0:/ 192.168.0.11:/: Invalid argument
But when I do this:
tong:~ # exportfs ting:/
Now it works!
Ok, so I can make it work by hand, but the trouble is still that the line in /etc/exports doesn't work on tong, but works on ting.
Ugh!
Thanks.
Christopher R. Carlen crobc@earthlink.net Suse 7.3 Linux 2.4.10
-- To unsubscribe send e-mail to suse-linux-e-unsubscribe@suse.com For additional commands send e-mail to suse-linux-e-help@suse.com Also check the archives at http://lists.suse.com