You are not logged in.
Pages: 1
I have successfully mounted an nfs share on /home in the past, it seemed to work fine apart from with firefox, which seems to take about a minuite to start, opera and epiphany also seem to suffer the same fate. They all work wonderfully once the app is open.
I would really like to get this setup working, i currently do a nasty work around with symlinking everywhere so the .mozilla files end up on the local machine. not ideal when the whole idea of a nfs /home is so you can have the same bookmarks etc everywhere you go.
Any ideas why? Anyone?
Thanks in advance to the ever great archers
Offline
Some brief Googling I did makes it look like a locking issue. This Red Hat thread is related to your problem.
Offline
thanks for that skymt. funny that i did some googling and came up with a similar result although it was with openoffice taking ages to start although i haven't got that installed. Do you think it is a problem with the nfs package in the arch repo's then?
Offline
Are rpc.lockd and rpc.statd running on the server? If not, (assuming you're running Arch on the server) add "nfslock" to the DAEMONS array in /etc/rc.conf. If they are, you may have a firewall issue like the fellow in the Red Hat support thread.
Offline
Sorry the reply took so long, i had to have a sleep in between.
I have checked all the above and i am still have problems both server and client both run arch. I don't see how it can be a firewall problem, nfs works fine for all other programs i can stream music / movies etc over fine. Plus i didn't think arch came with any firewall rules defined. I would need some real help here, iptables is something i have nether grasped in linux.
Many Thanks in advance
Offline
During setup, did you follow the directions on the Arch wiki, or somewhere else?
Also, what's in your /etc/hosts.allow file?
Offline
No i did not follow the arch wiki, basically because i have set up nfs loads of times before on other os. Here is my hosts.allow which should allow everything on my network range and my /etc/exports and my daemons line from /etc/rc.conf just incase.
#
# /etc/hosts.allow
#
ALL: 192.168.1.: ALLOW
# End of file
# /etc/exports
#
# See exports(5) for a description.
# use exportfs -arv to reread
/data/home 192.168.1.0/255.255.255.0(sync,rw,subtree_check)
DAEMONS=(syslog-ng portmap network netfs nfslock nfsd crond sshd webmin httpd rsyncd samba)
Last edited by gazj (2007-07-21 19:00:33)
Offline
Try adding the "insecure_locks" option to /etc/exports, just to help narrow down your problem.
Offline
Offline
Does your account have the same numeric UID on both systems?
And yeah, I'm running out of ideas. Sorry. My next one would be to try another technology, like Samba or AFS. Although if you've done this with NFS in the past, I don't see why it wouldn't work on Arch.
Offline
Offline
I've never done anything like this with Samba, but the access controls guide makes it look feasible.
You should also look at OpenAFS, which is more Unix-oriented than Samba and more modern than NFS.
Offline
Offline
AFS is a giant undertaking, and requires Kerberos to authenticate yourself to. I think it's overkill for this purpose.
Offline
Make sure nfslock is started on the client too.
:?
Offline
Just out of curiosity, are you using PAM and pam_mount?
If not, you should investigate. It's ideal for this sort of setup.
Offline
Pages: 1