Workspace - Revision history

H Schumacher: Changed formatting, added some information

2026-03-30T15:19:59Z

Changed formatting, added some information

H Schumacher: Added "groups" command

2026-02-27T12:13:55Z

Added "groups" command

← Older revision		Revision as of 14:13, 27 February 2026
Line 82:		Line 82:
	=== Regular Unix Permissions ===		=== Regular Unix Permissions ===

	Making workspaces world readable/writable using standard unix access rights with <tt>chmod</tt> is only feasible if you are in a research group and you and your co-workers share a common ("~~bwXXXXX~~") ~~unix group~~.		Making workspaces world readable/writable using standard unix access rights with <tt>chmod</tt> is only feasible if you are in a research group and you and your co-workers share a common unix group (for example "bw22a222").

	Do '''not''' make files readable or even writable to everyone or to large common groups ("all students").		Do '''not''' make files readable or even writable to everyone or to large common groups ("all students").
			You can see available groups with the command <code>groups</code>.

	{\| class="wikitable"		{\| class="wikitable"

K Siegmund: /* Setting Permissions for Sharing Files */

2026-02-24T10:00:45Z

Setting Permissions for Sharing Files

← Older revision		Revision as of 12:00, 24 February 2026
Line 69:		Line 69:
	* -G option of ws_allocate		* -G option of ws_allocate
	<code syntax=bash>ws_allocate -G groupname workspacename duration</code>		<code syntax=bash>ws_allocate -G groupname workspacename duration</code>

			e.g. for the group bw16e001 and for the workspace for 30 days:

			<code syntax=bash>ws_allocate -G bw16e001 commonfiles 30</code>

	** groupname: name of the group you want to share with		** groupname: name of the group you want to share with

K Siegmund: /* Create workspace */

2026-02-24T09:52:31Z

Create workspace

← Older revision		Revision as of 11:52, 24 February 2026
Line 6:		Line 6:

	== Create workspace ==		== Create workspace ==
			To create a workspace you need to state
⚫	~~To create a workspace you need to state ''name'' of your workspace and ''lifetime'' in days.~~ A maximum value for ''lifetime'' and a maximum number of renewals is defined on each cluster. Execution of:
			* ''name'' of your workspace and
			* ''lifetime'' in days.
		⚫	A maximum value for ''lifetime'' and a maximum number of renewals is defined on each cluster. Execution of:

	$ ws_allocate mySpace 30		$ ws_allocate mySpace 30

H Schumacher: Fixed typo

2025-11-22T16:18:13Z

Fixed typo

← Older revision		Revision as of 18:18, 22 November 2025
Line 1:		Line 1:
	'''Workspace tools''' provide temporary scratch space so ~~calles~~ '''workspaces''' for your calculation on a central file storage. They are meant to keep data for a limited time – but usually longer than the time of a single job run.		'''Workspace tools''' provide temporary scratch space so called '''workspaces''' for your calculation on a central file storage. They are meant to keep data for a limited time – but usually longer than the time of a single job run.

	== No Backup ==		== No Backup ==

	Workspaces are not meant for permanent storage, hence data in workspaces is not backed up and may be lost in case of problems on the storage system. Please copy/move important results to $HOME or ~~some~~ ~~disks~~ outside the cluster.		Workspaces are not meant for permanent storage, hence data in workspaces is not backed up and may be lost in case of problems on the storage system. Please copy/move important results to $HOME or storage space outside the cluster.

	== Create workspace ==		== Create workspace ==
Line 101:		Line 101:
	** rwx: read, write, execute		** rwx: read, write, execute

	=== ~~"ACL"s~~: Access ~~Crontrol~~ Lists ===		=== ACLs: Access Control Lists ===
	ACLs allow a much more detailed distribution of permissions but are a bit more complicated and not visible in detail via "ls". They have the additional advantage that you can set a "default" ACL for a directory, (with a <tt>-d</tt> flag or a <tt>d:</tt> prefix) which will cause all newly created files to inherit the ACLs from the directory. Regular unix permissions only have limited support (only group ownership, not access rights) for this via the suid bit.		ACLs allow a much more detailed distribution of permissions but are a bit more complicated and not visible in detail via "ls". They have the additional advantage that you can set a "default" ACL for a directory, (with a <tt>-d</tt> flag or a <tt>d:</tt> prefix) which will cause all newly created files to inherit the ACLs from the directory. Regular unix permissions only have limited support (only group ownership, not access rights) for this via the suid bit.

	Best practices with respect to ACL usage:		Best practices with respect to ACL usage:
	# Take into account that ~~ACL~~ take precedence over standard unix access rights		# Take into account that ACLs take precedence over standard unix access rights
	# The owner of a workspace is responsible for its content and management		# The owner of a workspace is responsible for its content and management

M Janczyk: Undo revision 15417 by M Janczyk (talk)

2025-11-18T10:57:03Z

Undo revision 15417 by M Janczyk (talk)

Show changes

M Janczyk: table with site features

2025-11-18T10:01:56Z

table with site features

Show changes

M Janczyk: /* List all your workspaces */

2025-10-22T12:05:14Z

List all your workspaces

← Older revision		Revision as of 14:05, 22 October 2025
Line 19:		Line 19:

	== List all your workspaces ==		== List all your workspaces ==

	To list all your workspaces, execute:		To list all your workspaces, execute:

Line 29:		Line 30:
	* creation date and remaining time		* creation date and remaining time

			To list expired workspaces, see [[Workspace#Restore_an_Expired_Workspace\|Restore an Expired Workspace]].

	== Find workspace location ==		== Find workspace location ==

K Siegmund: /* Workspace Tools */

2025-09-11T14:16:16Z

Workspace Tools

← Older revision		Revision as of 16:16, 11 September 2025
Line 56:		Line 56:

	* ws_share		* ws_share
	<code syntax=bash>ws_share share ~~workspacenamee~~ username</code>		<code syntax=bash>ws_share share workspacename username</code>

	allows you to grant the user username read access to the workspace.		allows you to grant the user username read access to the workspace.

K Siegmund: /* Workspace Tools */

2025-09-03T08:46:30Z

Workspace Tools

← Older revision		Revision as of 10:46, 3 September 2025
Line 68:		Line 68:
	** workspacename: what you want to call your workspace		** workspacename: what you want to call your workspace
	** duration: how long the workspace is supposed to last in days		** duration: how long the workspace is supposed to last in days

			Essentially this tool sets regular unix rwx permissions for the group plus the "suid" bit on the directory to make the permission inheritable.

	=== Regular Unix Permissions ===		=== Regular Unix Permissions ===