NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Solved
Mimic "Set ownership and permission for ...." in cron?
I previously posted an issue I was having with Backup errors https://community.netgear.com/t5/Using-your-ReadyNAS/Backup-FROM-ReadyNAS-NVX-to-OSX-with-NFS/m-p/1099388 I find now that whene...
If you run top and use the "c" toggle you can see that the commands are chown -R user:group /c/sharename and chmod -R xxx /c/sharename (xxx being determined by the permissions you set).
This still seems like the wrong solution to me. Why not just create a matching group on the mac? or reset the GID for staff?
I know I'm using a consistent credential on the Macs. The issue seems to be with the group id. The default when creating a file on the ReadyNAS is 103 (Gods). The default on the Mac is 20 (staff).
When the backup job happens from the ReadyNas to another Mac using Remote NFS (I tried Windows/NAS and couldn't get the connection to work) , the system attempts to preserve ownership. This fails because of the group owner of the files that have been added.
If I run the "Set ownership and permission for existing files and folders in this share to the above settings." where the group id is the group on the ReadyNAS with an id of 20 it fixes the problem.
This is why I'd like to just have a way to automate whatever command that uses. I just need to know what command it is running. I'm sure it's a chown but I'd like to know the exact paramaters so nothing else gets broken.
If you run top and use the "c" toggle you can see that the commands are chown -R user:group /c/sharename and chmod -R xxx /c/sharename (xxx being determined by the permissions you set).
This still seems like the wrong solution to me. Why not just create a matching group on the mac? or reset the GID for staff?
Thanks. I actually would have prefferred to change the Gods GID but 20 was used by something already.
I'm worried that changing the staff GID will create more headaches than it's worth. While not the most elegant solution, scheduling the command to run nightly will fix the problem.
20 is used by avahi on 4.2.x NAS.
I wouldn't be cautious messing with the default user/groups, since it could lead to side effects, and could come unglued later on if you need to do an OS reinstall.
Yeah. That's why I only set the file/directory owners in that one share I'm backing up to the matching UID/GID. I was able to match the UID easy enough without affecting any other UID but the GID as you pointed out is used by avahi
I don't think changing the owner on the share will impact anything else though which is why I think this is actually the safest way to make it work.
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!
