Note that there are some explanatory texts on larger screens.

plurals
  1. POFiles created through Cygwin (calling a shell script) don't have correct Windows permissions
    text
    copied!<p>I am currently running Cygwin on a target Windows Server 2003 machine to fire off a shell script that, among other things, creates a bunch of files on disc. However after the files are created I no longer have permissions to manipulate them through Windows.</p> <p>When the files are created the owner is getting set to 'SYSTEM' and the permissions for <code>Administrators/Creator Group/Creator Owner/system</code> are set to only 'special permissions' and nothing else. The permissions for Everyone and Users have Read &amp; Execute, List folder contents and Read.</p> <p>My problem is that I cannot delete/modify the files now through Windows. I would prefer to have something built into my scripts (either the shell script or something to call in Cygwin) that would allow Administrators full control on the folder and all contents. </p> <p>My current workaround has been to either do file modifications through Cygwin but this is not preferable. I have also used <code>setfacl -r -m default:other:rwx</code> to add write permissions for the 'Users' group but it doesn't appear to have a recursive option and still doesn't give 'full control'</p> <p>Is there a better way to use <code>setfacl</code>? Can I call the shell script using different/elevated permissions?</p> <p>Results of <code>getfacl</code> on a newly created directory:</p> <pre><code>$ getfacl Directory/ # file: Directory/ # owner: SYSTEM # group: root user::rwx group::r-x group:Users:rwx mask:rwx other:r-x default:user::rwx default:group::r-x default:group:Users:rwx default:mask:rwx default:other:r-x </code></pre>
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload