April 6, 201610 yr I set up some dockers and didn't realize permissions were screwed up. I've fixed that problem moving forward, but now I have a bunch of files on my array where write permission is only granted to 'nobody'. I don't know how to sign in as 'nobody', and my main account and the guest account can not modify these files. How do I sign in as 'nobody', and is there a way to batch alter permissions?
April 6, 201610 yr Author Is that the new permissions tool in the GUI for upgrading legacy systems, or something else?
April 7, 201610 yr I set up some dockers and didn't realize permissions were screwed up. I've fixed that problem moving forward, but now I have a bunch of files on my array where write permission is only granted to 'nobody'. I don't know how to sign in as 'nobody', and my main account and the guest account can not modify these files. How do I sign in as 'nobody', and is there a way to batch alter permissions? chmod and chown have the option for recursion. If you don't opt for the new permissions route you could run the recursive version on the directories that have the wrong permissions. Of course I think new perms just does the same thing... so...
April 7, 201610 yr Yes, newperms is available as a gui button. But if you use that it will traverse your entire /mnt directory I think. This is not always what you want it to do, as it might change permissions for docker or plugin appdata files, if you have them on cache or array. Instead you can use it on the console. newperms -> will set the default permissions as if you clicked on the button in the webui. newperms /mnt/disk1 -> will set the default permissions for the whole disk1 newperms /mnt/Movies -> will set the default permissions for your whole Movies share on all disks newperms /some/path/to/some/other/directory -> will set the default permissions for that directory and subdirs only.
April 7, 201610 yr Author Thank you very much, this worked. Yes, newperms is available as a gui button. But if you use that it will traverse your entire /mnt directory I think. This is not always what you want it to do, as it might change permissions for docker or plugin appdata files, if you have them on cache or array. Instead you can use it on the console. newperms -> will set the default permissions as if you clicked on the button in the webui. newperms /mnt/disk1 -> will set the default permissions for the whole disk1 newperms /mnt/Movies -> will set the default permissions for your whole Movies share on all disks newperms /some/path/to/some/other/directory -> will set the default permissions for that directory and subdirs only.
April 7, 201610 yr Yes, newperms is available as a gui button. But if you use that it will traverse your entire /mnt directory I think. This is not always what you want it to do, as it might change permissions for docker or plugin appdata files, if you have them on cache or array. Instead you can use it on the console. newperms -> will set the default permissions as if you clicked on the button in the webui. newperms /mnt/disk1 -> will set the default permissions for the whole disk1 newperms /mnt/Movies -> will set the default permissions for your whole Movies share on all disks newperms /some/path/to/some/other/directory -> will set the default permissions for that directory and subdirs only. Wow that's really good info, I had no idea that you could send additional information to the newperms script when you use it on console. Thanks for pointing that out!
April 7, 201610 yr It takes two other optional parameters too, namely user and group , so the full syntax is newperms [<path> [<user> [<group>]]] I'm curious about the very generous permissions it gives though, setting files to -rw-rw-rw- (666) and directories to drwxrwxrwx (777). The comments within the script explain how this is achieved in a rather round about way and there's a suggestion that the choice of permissions has evolved over time. I would prefer something like -rw-r--r-- (644) for files and drwxr-xr-x (755) for directories, myself. I'll try to find the original thread and work out out why they are so permissive and if they really need to be.
April 7, 201610 yr Community Expert Yes, newperms is available as a gui button. But if you use that it will traverse your entire /mnt directory I think. This is not always what you want it to do, as it might change permissions for docker or plugin appdata files, if you have them on cache or array. Instead you can use it on the console. newperms -> will set the default permissions as if you clicked on the button in the webui. newperms /mnt/disk1 -> will set the default permissions for the whole disk1 newperms /mnt/Movies -> will set the default permissions for your whole Movies share on all disks newperms /some/path/to/some/other/directory -> will set the default permissions for that directory and subdirs only. Just thought I should note that one of these examples is not exactly correct. There is no /mnt/Movies. It would be /mnt/user/Movies.
Archived
This topic is now archived and is closed to further replies.