nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Maintain permissions in Workarea

Sailesh

Hi,

If we have a file on window's desktop which has full permission for 'Everyone' and can the same permissions to be maintained when we import the same into our Teamsite workarea? Some how it is changing to 'rw-rw-r-- ' this is before we submit the file.

Folder has 'rwxrwxr-x' permissions set.

This file is getting imported and is not a teamsite created file.

Find more posts tagged with

Comments

Adam Stoller

Hi,

If we have a file on window's desktop which has full permission for 'Everyone' and can the same permissions to be maintained when we import the same into our Teamsite workarea? Some how it is changing to 'rw-rw-r-- ' this is before we submit the file.

Folder has 'rwxrwxr-x' permissions set.

This file is getting imported and is not a teamsite created file.

To begin with - Windows (your client desktop) and Unix (your server, apparently) use different mechanisms for permissions - so there is no way that you can expect Windows permissions to be maintained within the Unix environment when the file is imported.

Perhaps it would be better if you described the real issue here instead of what you think the issue is. My guess is that the problem could be resolved through proper use of Unix groups and chmod g+s on the directory(ies).

Sailesh

To begin with - Windows (your client desktop) and Unix (your server, apparently) use different mechanisms for permissions - so there is no way that you can expect Windows permissions to be maintained within the Unix environment when the file is imported.

Perhaps it would be better if you described the real issue here instead of what you think the issue is. My guess is that the problem could be resolved through proper use of Unix groups and chmod g+s on the directory(ies).

Thanks for update, really issue is that we want that every file which get created/uploaded to a particular folder should have execute bit on for others. Though the folder itself is been set with right permissions but any new file created inside this folder is not.

Adam Stoller

Thanks for update, really issue is that we want that every file which get created/uploaded to a particular folder should have execute bit on for others. Though the folder itself is been set with right permissions but any new file created inside this folder is not.

The submit.cfg can fix that for files that get submitted within that folder.
I don't know whether there's a magic chmod for that, but you might be able to add an iwat trigger script that verifies the directory into which newly created files were added to determine if it needs to run a chmod on them ...