May 13, 20242 yr Can I change the default permissions in the "new permissions" tool? I mean these: For directories: drwxrwxrwx For read/write files: -rw-rw-rw- For readonly files: -r--r--r-- I want them to be For read/write files: -rwxrwxrw- Can it be changed?
May 13, 20242 yr Community Expert There is no realistic way to change the permissions on that script. I do not understand why you want ‘execute’ permission on those files - I would expect it to be a serious security risk.
May 13, 20242 yr Community Expert Solution As I remember from 40+ years when I took a introductory course to UNIX, we had to change permissions on any file that we wanted to be executable. That include both Shell files and compiled C programs. (Yes, we actually compiled the "Hello Word" program in C!) So it is not a recent invocation that files by default do not have the execute bit set. You mention that you want to New Permissions script to retain (basically) the current permissions on the files. When it was designed, its intend was to set the permissions to 777 for directories and 666 for Files as well as setting the owner to 'nobody' and the group to 'users'. Furthermore, when it was first released, it was only intended to be used once when a major version upgrade to Unraid required that all the permissions, owner and group had to be changed for all of the files and directories. What has happened is that rogue Dockers, VMs (and even users) sometimes use different permissions owners and groups and these permissions can break the way Unraid is intended to work. It was found that the New Permissions script could quickly fix these problems and so it remained a part of the Unraid. If you require for some reason that you require non-standard permissions on certain files, you are just going to have to avoid running those scripts on the Shares that contain the files. (Beyond my comprehension why you would need execute permissions on file that are being stored in data array) Edited May 13, 20242 yr by Frank1940
May 13, 20242 yr Community Expert 1 hour ago, jarken said: For read/write files: -rw-rw-rw- For readonly files: -r--r--r-- How would it be supposed to guess what you want read-only and what you want read-write?
May 13, 20242 yr Author 14 minutes ago, Frank1940 said: As I remember from 40+ years when I took a introductory course to UNIX, we had to change permissions on any file that we wanted to be executable. That include both Shell files and compiled C programs. (Yes, we actually compiled the "Hello Word" program in C!) So it is not a recent invocation that files by default do not have the execute bit set. You mention that you want to New Permissions script to retain (basically) the current permissions on the files. When it was designed, its intend was to set the permissions to 777 for directories and 666 for Files as well as setting the owner to 'nobody' and the group to 'users'. Furthermore, when it was first released, it was only intended to be used once when a major version upgrade to Unraid required that all the permissions, owner and group had to be changed for all of the files and directories. What has happened is that rogue Dockers, VMs (and even users) sometimes use different permissions owners and groups and these permissions can break the way Unraid is intended to work. It was found that the New Permissions script could quickly fix these problems and so it remained a part of the Unraid. If you require for some reason that you require non-standard permissions on certain files, you are just going to have to avoid running those scripts on the Shares that contain the files. (Beyond my comprehension why you would need execute permissions on file that are being stored in data array) Its because plex in docker, cannot use the codecs to transcode if the execution permission is not applied. That's why I was asking, I had to apply these permissions by hand after running it (New Permissions script), I will keep this in mind for the next time I run it.
May 13, 20242 yr Community Expert 59 minutes ago, jarken said: Its because plex in docker, cannot use the codecs to transcode if the execution permission is not applied. That's why I was asking, I had to apply these permissions by hand after running it (New Permissions script), I will keep this in mind for the next time I run it. These would be in appdata and you should never run the New Permissions tool on the appdata share as it'll wreck everything, various containers requiring completely different permissions. Edited May 13, 20242 yr by Kilrah
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.