On 01/29/10 04:45, Huub wrote:
> I hope this is the correct group posting to.
No. NFS is a file-system technology, and is distinct from networking.
You want the NFS group:
http://hub.opensolaris.org/bin/view/Community+Group+nfs/
[email protected]
> I get this error after mount -a :
>
> nfs mount: Kaapstad:/admin: No such file or directory
I would use "showmount -e Kaapstad" to make sure that system really is
exporting those file systems in a way that we can see, and then
"wireshark" to see what goes wrong during the mount process.
I think it's better to get a cause of the problem first, rather than
just modifying arbitrary things to see if it changes.
> Kaapstad is in the /etc/hosts file, so that's no problem. However,
> looking at nfs:
>
>> ps -ef | grep nfs
>> daemon 282 1 0 09:02:26 ? 0:00 /usr/lib/nfs/lockd
>> daemon 265 1 0 09:02:26 ? 0:00 /usr/lib/nfs/nfsmapid
>> daemon 271 1 0 09:02:26 ? 0:00 /usr/lib/nfs/nfs4cbd
>> daemon 267 1 0 09:02:26 ? 0:00 /usr/lib/nfs/statd
>
> Makes me suspect I have nfs4 running, instead of nfs3. And the server
> doesn't accept nfs4 connections. Can I safely (and easily) replace nfs4
> by nfs3?
You shouldn't need to. The system is supposed to switch between NFS
versions (4, 3, 2) as needed. I suspect that something else is amiss.
But, if you insist, "man nfs" suggests that the /etc/default/nfs file
can be used to tune the available NFS versions. Setting
NFS_CLIENT_VERSMAX=3 should do it.
--
James Carlson 42.703N 71.076W <[email protected]>
_______________________________________________
networking-discuss mailing list
[email protected]
