I know that this has been discussed but I don't think an actual defect report has ever been created.  So, here I am. 

 

I occasionally need to run the New Permissions script on my cache dir due to not having rights to some of my docker settings folder from another machine.  I also have some shell scripts in these folders which I had previously chmod +x.

 

After running the new perms script, my shells script lose their +x attribute.  I guess this is expected since the description of the scriupt explains this:

 

This utility starts a background process that goes to each of your data disks and cache disk and changes file and directory ownership to nobody/users (i.e., uid/gid to 99/100), and sets permissions as follows:

 

For directories:

  drwxrwxrwx

 

For read/write files:

  -rw-rw-rw-

 

For readonly files:

  -r--r--r--

 

Is there a better solution for things such as the cache drive which often house executable scripts?  Or is it just a mater of knowing what files you are running the script against?

 

John

I know that this has been discussed but I don't think an actual defect report has ever been created.  So, here I am. 

 

I occasionally need to run the New Permissions script on my cache dir due to not having rights to some of my docker settings folder from another machine.  I also have some shell scripts in these folders which I had previously chmod +x.

 

After running the new perms script, my shells script lose their +x attribute.  I guess this is expected since the description of the scriupt explains this:

 

This utility starts a background process that goes to each of your data disks and cache disk and changes file and directory ownership to nobody/users (i.e., uid/gid to 99/100), and sets permissions as follows:

 

For directories:

  drwxrwxrwx

 

For read/write files:

  -rw-rw-rw-

 

For readonly files:

  -r--r--r--

 

Is there a better solution for things such as the cache drive which often house executable scripts?  Or is it just a mater of knowing what files you are running the script against?

 

John

 

We are investigating a few ways to address this.  Short term, the new permissions script does exactly what you posted in the quote, so this isn't a defect, but rather, how the system works by design.

 

The real issue here is here:

 

due to not having rights to some of my docker settings folder from another machine

 

Please elaborate on this issue further so we can better understand the need.