Difference between revisions of "Tips: Custom file permissions at creation"

 
(13 intermediate revisions by 2 users not shown)
Line 1: Line 1:
{{color box |lightsteelblue|[[:Template:Stub]] This is a stub page and needs expansion}}
+
This page provides information on how to create files with group read permissions at NCI.
== NCI projects ==
 
The base unit for the accounting of computational and storage resources is the project. There are 2 types of projects at NCI:
 
* data projects: for published and shared datasets
 
* computational projects: for running programs
 
To have a valid login at NCI, you need to be a member of at least one computational project.
 
=== CLEx projects ===
 
CLEx is managing several computational and data projects at NCI via the CMS team. We will not list the data projects since you do not have write access to any of those. To find datasets published at NCI, please see the information on [[Data_Access|this page]]
 
  
The computational projects are split by Research Program (RP):
+
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.
{| class="wikitable"
+
 
|-
+
== PBS logs ==
! Project !! RP !! Lead CI
+
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:
| v45 || Extra-tropical variability || [mailto:andy.hogg@anu.edu.au Andy Hogg]
+
<syntaxhighlight lang=text>
|-
+
#PBS -W umask=0022
| w35 || Drought || [mailto:c.carouge@unsw.edu.au Claire Carouge]
+
</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.
| w40 || Extreme Rainfall || [mailto:martin.jucker@unsw.edu.au Martin Jucker]
+
 
|-
+
== Files created by programs ==
| w42 || Extreme Rainfall || [mailto:abhnil.prasad@unsw.edu.au Abhnil Prasad]
+
 
|-
+
Some programs might impose a different default of the files they create which might not be what you'd like.
| w48 || Tropical Variability || [mailto:dietmar.dommenget@monash.edu Dietmar Dommenget]
+
 
|-
+
=== You have access to the source code ===
| w97 || Heatwaves || [mailto:jason.evans@unsw.edu.au Jason Evans]
+
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:Stub]]
+
=== 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]]

Latest 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.

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>