If you want to run an NFS share from a Mac, yes, it's a bit more difficult. The NFS shares don't appear in Network browser, but can be accessed via " Go / Connect to server / nfs:///share" no login needed or permissions hassles (we're not using it, because AFP works fine for us - but it's available if AFP craps out). That's what I got out of the QNAP box to a bunch of macs ranging from OS X Tiger (10.4) to the latest Yosemite. Schumaku wrote:that's not a click and play project If we're talking about NFS access to QNAP shares, and all that is required is *guest* access from Macs then yes, it is a "click and play project", as you put it. Please head out and read about NFS(v3) and it's management first - or better forget about it. ) _and_ NFS concurrently on the same data - that's not a click and play project. Seriously - especially in case you intend to use NAS based access (QTS Web, Apps, SAMBA, AFP.
Nfs manager for yosemite manual#
Don't use NFS - to set-up a proper NFS environment you need a lot of manual work, getting uid and gid in sync, use the same group names, the same usernames.
NFS does fully build on the _client_ side uid and gid of the user accessing - this is completely unrelated to the access rights, the usernames (including uid), and the group (including gid), configured on the NAS and it's sharing services. Now I am very confused as to why a user I put in the admin group, which has RW rights, and the user had RW rights but still can't edit it. BurningSky wrote:I added a user to be used for the smb to test if I could get it working and got the same peculiarities in that I could navigate to the files but not edit them, even though the user was set to have RW rights, then I changed the smb mount to auth using the admin account and it let me edit the file.