This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision |
| technical:generic:workgroup-cmd [2020-07-23 14:10] – frey | technical:generic:workgroup-cmd [2020-07-23 16:15] (current) – [Alterations to the workgroup Command] anita |
|---|
| ====== Alterations to the workgroup Command ====== | ====== Alterations to the workgroup Command ====== |
| |
| Users of the IT-RCI clusters have a primary gid (group id) of //everyone// (or //900//), but when submitting and executing jobs the user needs an effective gid other than that. The ''workgroup'' command is used to execute a command or spawn a new shell that has an effective gid of a secondary group of which the user is a member. For example, a member of the ``it_nss`` workgroup on Caviness can do the following: | Users of the IT-RCI clusters have a primary gid (group id) of //everyone// (or //900//), but when submitting and executing jobs the user needs an effective gid other than that. The ''workgroup'' command is used to execute a command or spawn a new shell that has an effective gid of a secondary group of which the user is a member. For example, a member of the ''it_nss'' workgroup on Caviness can do the following: |
| |
| <code bash> | <code bash> |
| ===== Issues ===== | ===== Issues ===== |
| |
| One issue with the ``workgroup`` command is in the inheritance of the environment. The Bash shell environment includes unexported variables, aliases, array-valued variables, and functions that are not a part of the POSIX environment that sub-processes will inherit: | One issue with the ''workgroup'' command is in the inheritance of the environment. The Bash shell environment includes unexported variables, aliases, array-valued variables, and functions that are not a part of the POSIX environment that sub-processes will inherit: |
| |
| <code bash> | <code bash> |