James Carlson <[email protected]> writes: > A quick search on that error message and the word "linux" turns up > at least one good hit: > > https://bugzilla.redhat.com/show_bug.cgi?format=multiple&id=467613 > > It seems that it's a known problem with the Linux NFS server, and that > adding "sec=sys" on the server side should fix it.
Yikes, I feel kind of stupid for not having searched on the error... and I have done that many times before, so it was a lame oversight. Thanks for your help. I'm running Gentoo linux not redhat, on the server so it may not apply but if it's a problem with the linux implementation of NFS, it might be the same thing. I did notice that latest few linux kernels now have options you can activate to allow nfs4. That might be a way to go too. oh.. I tried the fix mentioned there and mounted without error. So looks like I'm in business sort of... That kind of mount using this command: mount -F nfs reader:/pub /pub results in a mounted filesystem that cannot be written to by users. The user is denied the right to mount the share themselves. After stumbling my way through mount_nfs looking for options that seem like they might mount the share in such a way that users could write there, I wasn't at all sure which if any options would do that. With the above command the share is mounted wuth UID=1000 and GID=staff. I'm far from understanding the user/roles stuff available in solaris too. How can I accomplish an nfs mount where users can write to it. Or at least a specific user besides root. This is all happening on a firewall protected home lan so both server and client are not available to the internet. Security is not a big factor. _______________________________________________ networking-discuss mailing list [email protected]
