Difference between revisions of "Tips: Custom file permissions at creation"
| (13 intermediate revisions by 2 users not shown) | |||
| Line 1: | Line 1: | ||
| − | + | This page provides information on how to create files with group read permissions at NCI. | |
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | + | By default, when you create a file under /short of /g/data, the file will be readable by you and the group owning the file. So you don't need to change anything then. But there are a few cases where the default behaviour is different and you may want to change it. | |
| − | + | ||
| − | + | == PBS logs == | |
| − | + | By default, all log files from PBS are only readable by the user owning the file. | |
| − | + | You can use a PBS option to change this behaviour so your logs are readable by the user and the group owning the file: | |
| − | + | <syntaxhighlight lang=text> | |
| − | + | #PBS -W umask=0022 | |
| − | + | </syntaxhighlight> | |
| − | + | You need to add this option either to the script you submit to the queue (with qsub) or directly to the qsub command line. | |
| − | + | ||
| − | + | == Files created by programs == | |
| − | + | ||
| − | + | Some programs might impose a different default of the files they create which might not be what you'd like. | |
| − | + | ||
| − | + | === You have access to the source code === | |
| − | + | If you have access to the source code, it is usually possible to modify the default behaviour. What needs to be modified varies depending on the language. Please contact [mailto:cws_help@nci.org.au the CMS team] if you need help. | |
| − | + | ||
| − | [[Category: | + | === You don't have access to the source code === |
| + | You then need to add a post-processing step, for example in a bash script calling your program. You can change the permissions on the files created by your program, using the <code>chmod</code> command: | ||
| + | chmod g+r <filename> | ||
| + | This command can be run recursively through a directory tree: | ||
| + | chmod -R g+r <directory_name> | ||
| + | |||
| + | === Files owned by the wrong group === | ||
| + | If you are using compute time from several projects, you may end up with files owned by different projects in the same area. This might not be the ideal situation for you and it is possible to change the group owning the file. '''Note:''' NCI's storage accounting depends only on the group owning the files and not the project space under which the files are stored. '''Before changing the group owning files, please make sure the new group has enough free allocation and you will not cause that group to get over quota.''' | ||
| + | |||
| + | To change the group ownership of a file: | ||
| + | chgrp <newgroup> <filename> | ||
| + | Or recursively through a directory tree: | ||
| + | chgrp -R <newgroup> <directory_name> | ||
| + | |||
| + | [[Category:Data]] | ||
Revision as of 00:44, 12 December 2019
This page provides information on how to create files with group read permissions at NCI.
By default, when you create a file under /short of /g/data, the file will be readable by you and the group owning the file. So you don't need to change anything then. But there are a few cases where the default behaviour is different and you may want to change it.
Contents
PBS logs
By default, all log files from PBS are only readable by the user owning the file. You can use a PBS option to change this behaviour so your logs are readable by the user and the group owning the file:
#PBS -W umask=0022
You need to add this option either to the script you submit to the queue (with qsub) or directly to the qsub command line.
Files created by programs
Some programs might impose a different default of the files they create which might not be what you'd like.
You have access to the source code
If you have access to the source code, it is usually possible to modify the default behaviour. What needs to be modified varies depending on the language. Please contact the CMS team if you need help.
You don't have access to the source code
You then need to add a post-processing step, for example in a bash script calling your program. You can change the permissions on the files created by your program, using the chmod command:
chmod g+r <filename>
This command can be run recursively through a directory tree:
chmod -R g+r <directory_name>
Files owned by the wrong group
If you are using compute time from several projects, you may end up with files owned by different projects in the same area. This might not be the ideal situation for you and it is possible to change the group owning the file. Note: NCI's storage accounting depends only on the group owning the files and not the project space under which the files are stored. Before changing the group owning files, please make sure the new group has enough free allocation and you will not cause that group to get over quota.
To change the group ownership of a file:
chgrp <newgroup> <filename>
Or recursively through a directory tree:
chgrp -R <newgroup> <directory_name>
