Sharing data/fr: Difference between revisions

Jump to navigation Jump to search
Updating to match new version of source page
(Created page with "Dans les cas de partage de données plus complexes (avec plusieurs utilisateurs sur plusieurs grappes), il est possible de créer un '''groupe de partage'''. Il s'agit d'un gr...")
(Updating to match new version of source page)
Line 142: Line 142:


=== Change of the default <code>umask</code> on Cedar, Béluga and Niagara ===
=== Change of the default <code>umask</code> on Cedar, Béluga and Niagara ===
In the summer 2019, we discovered that the default <code>umask</code> was not the same on all Compute Canada servers. On October 16th, 2019, we will be changing the default <code>umask</code> on these three servers to match the one from Graham. The default <code>umask</code> will change as follows:  
In the summer 2019, we discovered that the default <code>umask</code> was not the same on all Compute Canada servers. On October 16th, 2019, we changed the default <code>umask</code> on these three servers to match the one from Graham. The default <code>umask</code> changed as follows:  
{| class="wikitable"
{| class="wikitable"
|-
|-
Line 154: Line 154:
|-
|-
|}
|}
This will mean that more restrictive permissions will be enforced on newly created files. If you need more permissive permissions for your workflow, you can change your default <code>umask</code> in your <code>.bashrc</code>. Our general advice is however to keep the default permissions.  
This means that more restrictive permissions are enforced on newly created files. If you need more permissive permissions for your workflow, you can change your default <code>umask</code> in your <code>.bashrc</code>. Our general advice is however to keep the default permissions.  


Note that this change does ''not'' mean that your files have been inappropriately exposed in the past. Restrictive access permissions have been set on your home, project, and scratch directories since the beginning.  Unless the permissions were changed to give ''execute'' permission on one of these folders to others, your files still cannot be accessed by other people.
Note that this change does ''not'' mean that your files have been inappropriately exposed in the past. Restrictive access permissions have been set on your home, project, and scratch directories since the beginning.  Unless the permissions were changed to give ''execute'' permission on one of these folders to others, your files still cannot be accessed by other people.
38,760

edits

Navigation menu