LWP-Wiki - User contributions [en]

Sharing directories

2025-04-30T09:50:18Z

Heiko:

[[Category:misc-faq]]
If you need to share a directory between a number of people, you can use part of your home directory. 
You can also ask for a separate, appropriately-named, directory outside of your homedir, of which you will be the owner. More information on how to do that can be found [[Project Directories| here]]. 
You can grant others access by using '''Access Control Lists''', '''ACLs''' from here on. Granting access using these NFS-ACL's can look daunting. A script called "share" is offered to hide NFS-ACL's complexity for common cases. The script "share" is located in /opt/netapps/bin which should normally be in your $PATH .

== How to use NFSv4 ACLs ==
You can find a detailed manual [https://www.osc.edu/resources/getting_started/howto/howto_use_nfsv4_acl here]. 
On the command-line you can give the following command to get more abbreviated usage information and some examples:
info nfs4_setfacl

== Some examples of more commonly used commands ==
To allow someone read access to a file or directory:
nfs4_setfacl -a A::'''<username>'''@rug.nl:RX '''<dir/file>'''
''Note: Use upper case '''RWX''' instead of lower case.''

It is possible to set 'default' ACLs. New files and/or sub-directories can automatically inherit these ACLs. 
To have new sub-directories inherit the ACL of it's parent:
nfs4_setfacl -a A:d:'''<username>'''@rug.nl:RX '''<dir>'''
And to have new files inherit the ACL:
nfs4_setfacl -a A:f:'''<username>'''@rug.nl:R '''<dir>'''

The ACLs can also be edited by using the editor command:
nfs4_editfacl '''<dir/file>'''
''Note: Altough you'll see different permission options, you can just use '''RWX''', this gets translated for you automatically when you save your edit.''

Sharing directories

2025-04-30T09:49:35Z

Heiko:

[[Category:misc-faq]]
If you need to share a directory between a number of people, you can use part of your home directory. 
You can also ask for a separate, appropriately-named, directory outside of your homedir, of which you will be the owner. More information on how to do that can be found [[Project Directories| here]]. 
You can grant others access by using '''Access Control Lists''', '''ACLs''' from here on. Granting access using these NFS-ACL's can look daunting. A script called "share" is offered to hide t NFS-ACL's for common cases. The script "share" is located in /opt/netapps/bin which should normally be in your $PATH .

== How to use NFSv4 ACLs ==
You can find a detailed manual [https://www.osc.edu/resources/getting_started/howto/howto_use_nfsv4_acl here]. 
On the command-line you can give the following command to get more abbreviated usage information and some examples:
info nfs4_setfacl

== Some examples of more commonly used commands ==
To allow someone read access to a file or directory:
nfs4_setfacl -a A::'''<username>'''@rug.nl:RX '''<dir/file>'''
''Note: Use upper case '''RWX''' instead of lower case.''

It is possible to set 'default' ACLs. New files and/or sub-directories can automatically inherit these ACLs. 
To have new sub-directories inherit the ACL of it's parent:
nfs4_setfacl -a A:d:'''<username>'''@rug.nl:RX '''<dir>'''
And to have new files inherit the ACL:
nfs4_setfacl -a A:f:'''<username>'''@rug.nl:R '''<dir>'''

The ACLs can also be edited by using the editor command:
nfs4_editfacl '''<dir/file>'''
''Note: Altough you'll see different permission options, you can just use '''RWX''', this gets translated for you automatically when you save your edit.''

Sharing directories

2025-04-30T09:49:03Z

Heiko:

[[Category:misc-faq]]
If you need to share a directory between a number of people, you can use part of your home directory. 
You can also ask for a separate, appropriately-named, directory outside of your homedir, of which you will be the owner. More information on how to do that can be found [[Project Directories| here]]. 
You can grant others access by using '''Access Control Lists''', '''ACLs''' from here on. Granting access using these NFS-ACL's can look daunting. A script called "share" is offered to hide t NFS-ACL's for common cases. The script "share" is located in /opt/netapps/bin which should normally be in your $PATH .

== How to use NFSv4 ACLs ==
You can find a detailed manual [https://www.osc.edu/resources/getting_started/howto/howto_use_nfsv4_acl here]. 
On the command-line you can give the following command to get more abbreviated usage information and some examples:
info nfs4_setfacl

== Some examples of more commonly used commands ==
To allow someone read access to a file or directory:
nfs4_setfacl -a A::'''<username>'''@rug.nl:RX '''<dir/file>'''
''Note: Use upper case '''RWX''' instead of lower case.''

It is possible to set 'default' ACLs. New files and/or sub-directories can automatically inherit these ACLs. 
To have new sub-directories inherit the ACL of it's parent:
nfs4_setfacl -a A:d:'''<username>'''@rug.nl:RX '''<dir>'''
And to have new files inherit the ACL:
nfs4_setfacl -a A:f:'''<username>'''@rug.nl:R '''<dir>'''

The ACLs can also be edited by using the editor command:
nfs4_editfacl '''<dir/file>'''
''Note: Altough you'll see different permission options, you can just use '''RWX''', this gets translated for you automatically when you save your edit.''

Data retention policy

2025-02-13T13:38:03Z

Heiko:

[[Category:home-directory-faq]]
== RUG account life cycle and your home directory ==

==== Summary / TL;DR: ====

When you leave the university your home directory may be deleted
permanently after 2 years, but not before .

===== Details: =====

Your general RUG account (p/s/f/g number account) is used to log
in to an LWP and is subject to the general university policy
governing these accounts. When you leave the university for any
reason your account will be disabled.

When your account has been disabled for more than 6 consecutive
months we may archive your home directory. This means it will be
compressed and put aside.

In case your account becomes enabled once again after your home
directory was archived, we can reinstate the home directory
manually on request.

When your account has been disabled for two or
more consecutive years we may delete your home directory and/or its archive
entirely and permanently. It will still be possible to restore it
from tape backup up for to 3 months after this, but this will
only be done under exceptional circumstances.

You will *not* recieve any warnings about this, since disabling
RUG accounts is already accompanied with warning emails.

===== Backup: =====

Backups are made every night of both home and project directories:

* Over the last 30 days a backup of every day is restorable.
* A backup of very week is restorable from 30 days ago to 60 days ago.
* One backup is kept available to a maximum of 90 days.

===== Note: =====

CIT offers a service for archiving research related data. For more information see:

* https://wiki.hpc.rug.nl/rdms/access/start

Data retention policy

2025-01-22T11:13:58Z

Heiko: /* Backup: */

[[Category:home-directory-faq]]
== RUG account life cycle and your home directory ==

==== Summary / TL;DR: ====

When you leave the university your home directory may be deleted
permanently after 2 years (but not before).

===== Details: =====

Your general RUG account (p/s/f/g number account) is used to log
in to an LWP and is subject to the general university policy
governing these accounts. When you leave the university for any
reason your account will be disabled.

When your account has been disabled for more than 6 consecutive
months we may archive your home directory. This means it will be
compressed and put aside.

In case your account becomes enabled once again after your home
directory was archived, we can reinstate the home directory
manually on request.

When your account has been disabled for two or
more consecutive years we may delete your home directory and/or its archive
entirely and permanently. It will still be possible to restore it
from tape backup up for to 3 months after this, but this will
only be done under exceptional circumstances.

You will *not* recieve any warnings about this, since disabling
RUG accounts is already accompanied with warning emails.

===== Backup: =====

'' '''NOTE: The following may change beginning 2025 !''' ''

Tape backups are made every night of both home and project directories:

* The last 7 versions of existing files are retained up to 30 days.
* The single last version of deleted files are retained up to 60 days.

===== Note: =====

CIT offers a service for archiving research related data. For more information see:

* https://wiki.hpc.rug.nl/rdms/access/start

Data retention policy

2025-01-22T11:13:40Z

Heiko: /* Backup: */

[[Category:home-directory-faq]]
== RUG account life cycle and your home directory ==

==== Summary / TL;DR: ====

When you leave the university your home directory may be deleted
permanently after 2 years (but not before).

===== Details: =====

Your general RUG account (p/s/f/g number account) is used to log
in to an LWP and is subject to the general university policy
governing these accounts. When you leave the university for any
reason your account will be disabled.

When your account has been disabled for more than 6 consecutive
months we may archive your home directory. This means it will be
compressed and put aside.

In case your account becomes enabled once again after your home
directory was archived, we can reinstate the home directory
manually on request.

When your account has been disabled for two or
more consecutive years we may delete your home directory and/or its archive
entirely and permanently. It will still be possible to restore it
from tape backup up for to 3 months after this, but this will
only be done under exceptional circumstances.

You will *not* recieve any warnings about this, since disabling
RUG accounts is already accompanied with warning emails.

===== Backup: =====

'''NOTE: The following may change beginning 2025 !''' ''Italic text''

Tape backups are made every night of both home and project directories:

* The last 7 versions of existing files are retained up to 30 days.
* The single last version of deleted files are retained up to 60 days.

===== Note: =====

CIT offers a service for archiving research related data. For more information see:

* https://wiki.hpc.rug.nl/rdms/access/start

Remote desktop access with NoMachine

2024-09-26T14:37:03Z

Heiko:

[[Category:remotexs-faq]]

'''Make sure your account name (P-nummer) is listed in the file /etc/users_allowed_ssh'''. You can edit this file only when logged in using the physical keyboard of the computer.

Download and install the NoMachine Enterprise Client for your system: 
https://www.nomachine.com/download-enterprise#NoMachine-Enterprise-Client 
 
''Note: The normal client will also install a NX server on your machine, so unless you want remote desktop access to your own PC as well, use the enterprise client.'' 

After you've installed the NoMachine client, open it and add a new connection. 
[[File:NX first screen.png|thumb|none|Initial screen.]]
Enter a '''Name''' for the connection and add the '''hostname or IP number''' for the '''Host''' you are trying to connect to. 
[[File:NX add connection.png|thumb|none|Add connection.]]
* Port = 4000
* Protocol = NX
[[File:NX configuration.png|thumb|none|Configuration.]]
Next select '''Configuration'''. Make sure '''Use password authentication''' is selected and '''Use UDP communication for multimedia data''' is checked. 
Click '''Connect'''.
[[File:Nx verify host authenticity.png|thumb|none|Verify your hosts identity.]]
The '''Verify host authenticity''' will only appear the first time you connect to your host or if you reinstall the host. If it does appear a second time on the same host, do not continue, this might indicate malicious activity on the host system and you should call support. 
Click '''Yes''' to verify your hosts identity.
[[File:Nx login.png|thumb|none|The login screen.]]
Enter your '''Username''' and '''Password''' and click '''Login'''. Don't save your password if you're on a shared PC.
[[File:NX connection setup audio.png|thumb|none|Audio on remote host.]]
Hit the checkbox to mute audio on the remote host. 
Hit the checkbox at the bottom left so this message does not appear again. Hit '''OK'''.
[[File:NX connection setup display.png|thumb|none|Scale remote desktop to fit window.]]
Select '''Scale the remote desktop to fit into the window'''. 
Hit the checkbox at the bottom left so this message does not appear again. Hit '''OK'''.
[[File:NX connection setup remote display.png|thumb|none|Don't resize remote display.]]
Select '''Don't resize the remote display'''. 
Hit the checkbox at the bottom left so this message does not appear again. 
Hit '''OK''' a last time to connect to the desktop of your remote host.
[[File:NX connection settings.png|thumb|none|Change connection setting from top right corner.]]
Now you can login as you would normally login on your LWP. 
If you want to change any of the connection settings, hover over the top right corner of the window until it folds down and then click it.

Getting to your Windows Y:-drive

2023-07-17T11:59:15Z

Heiko:

[[Category:misc-faq]]
When you use the LWP then your UWP Y: drive is available at '''/media/ydrive'''.

Otherwise from with the university network you can use the smb protocol to access the Y:-drive.
<code>
sudo mkdir -p /mnt/ydrive/
sudo mount -t smb3 //workspace.rug.nl/ydrive /mnt/ydrive/ -o user=<p-number>
</code>
From outside the university you can use https://vlwp.rug.nl or https://uwp.rug.nl

Getting to your Windows Y:-drive

2023-07-17T11:56:15Z

Heiko:

[[Category:misc-faq]]
When you use the LWP then your UWP Y: drive is available at '''/media/ydrive'''.

Otherwise from with the university network you can use the smb protocol to access the Y:-drive.
<code>
sudo mount -t smb3 //workspace.rug.nl/ydrive /mnt/ydrive/ -o user=<p-number>
</code>
From outside the university you can use https://vlwp.rug.nl or https://uwp.rug.nl

Getting to your Windows Y:-drive

2023-07-17T11:56:01Z

Heiko: Update the generic way to mount on linux

[[Category:misc-faq]]
When you use the LWP then your UWP Y: drive is available at '''/media/ydrive'''.

Otherwise from with the university network you can use the smb protocol to access the Y:-drive.

<code>
sudo mount -t smb3 //workspace.rug.nl/ydrive /mnt/ydrive/ -o user=<p-number>
</code>

From outside the university you can use https://vlwp.rug.nl or https://uwp.rug.nl

Main Page

2023-04-03T08:42:22Z

Heiko:

[[Category:Main]]
= LWP Wiki =
Welcome to the LWP-Wiki!! For general LWP information, [http://myuniversity.rug.nl/infonet/medewerkers/ict/werkplek/werkplekken/linuxwerkplek/ the LWP main page] is the starting point. 
If you're having trouble on your LWP, our [[FAQ]] is a good place to take a look first. We might already have solved your problem once or twice before. 


== Announcements ==
{{Announcement| [[User:Chris|Chris]] ([[User talk:Chris|talk]]) 17:01, 13 March 2023 (CET)| What if there was a way to avoid having to install a broad range of scientific software from scratch on every HPC cluster or cloud instance you use or maintain, without compromising on performance? Check out [[EESSI]]!}}
{{Announcement| [[User:Chris|Chris]] ([[User talk:Chris|talk]]) 11:13, 2 March 2022 (CET)|New version of PyMOL, v2.5.0, available on LWP. Employees of FSE will get the licensed version, v2.5.2.}}
{{Announcement|[[User:Chris|Chris]] ([[User talk:Chris|talk]]) 11:17, 7 April 2021 (CEST)|The new manual on how to install the latest version of the LWP is online [[Installing the LWP|here]].}}

If you're having trouble with your LWP and the solution isn't in our [[FAQ]], contact us by using the '''support''' program on the LWP's (if possible) by entering "support" on a LWP command line or selecting it from the menu. 
For more general questions you can contact us by sending a mail to [mailto:lwp@rug.nl lwp@rug.nl].

Data retention policy

2022-10-19T12:39:37Z

Heiko:

[[Category:home-directory-faq]]
== RUG account life cycle and your home directory ==

==== Summary / TL;DR: ====

When you leave the university your home directory may be deleted
permanently after 2 years (but not before).

===== Details: =====

Your general RUG account (p/s/f/g number account) is used to log
in to an LWP and is subject to the general university policy
governing these accounts. When you leave the university for any
reason your account will be disabled.

When your account has been disabled for more than 6 consecutive
months we may archive your home directory. This means it will be
compressed and put aside.

In case your account becomes enabled once again after your home
directory was archived, we can reinstate the home directory
manually on request.

When your account has been disabled for two or
more consecutive years we may delete your home directory and/or its archive
entirely and permanently. It will still be possible to restore it
from tape backup up for to 3 months after this, but this will
only be done under exceptional circumstances.

You will *not* recieve any warnings about this, since disabling
RUG accounts is already accompanied with warning emails.

===== Backup: =====

Tape backups are made every night of both home and project directories:

* The last 7 versions of existing files are retained up to 30 days.
* The single last version of deleted files are retained up to 60 days.

===== Note: =====

CIT offers a service for archiving research related data. For more information see:

* https://wiki.hpc.rug.nl/rdms/access/start

Data retention policy

2022-10-19T12:18:05Z

Heiko:

[[Category:home-directory-faq]]
== RUG account life cycle and your home directory ==

==== Summary / TL;DR: ====

When you leave the university your home directory may be deleted
permanently after 2 years (but not before).

===== Details: =====

Your general RUG account (p/s/f/g number account) is used to log
in to an LWP and is subject to the general university policy
governing these accounts. When you leave the university for any
reason your account will be disabled.

When your account has been disabled for more than 6 consecutive
months we may archive your home directory. This means it will be
compressed and put aside.

In case your account becomes enabled once again after your home
directory was archived, we can reinstate the home directory
manually on request.

When your account has been disabled for two or
more consecutive years we may delete your home directory and/or its archive
entirely and permanently. It will still be possible to restore it
from tape backup up for to 3 months after this, but this will
only be done under exceptional circumstances.

You will *not* recieve any warnings about this, since disabling
RUG accounts is already accompanied with warning emails.

===== Backup: =====

Tape backups are made every night of both home and project directories:

- The last 7 versions of existing files are retained up to 30 days.
- The single last version of deleted files are retained up to 60 days.

===== Note: =====

CIT offers a service for archiving research related data. For more information see:

* https://wiki.hpc.rug.nl/rdms/access/start

Data retention policy

2022-10-19T12:17:39Z

Heiko:

[[Category:home-directory-faq]]
== RUG account life cycle and your home directory ==

==== Summary / TL;DR: ====

When you leave the university your home directory may be deleted
permanently after 2 years (but not before).

===== Details: =====

Your general RUG account (p/s/f/g number account) is used to log
in to an LWP and is subject to the general university policy
governing these accounts. When you leave the university for any
reason your account will be disabled.

When your account has been disabled for more than 6 consecutive
months we may archive your home directory. This means it will be
compressed and put aside.

In case your account becomes enabled once again after your home
directory was archived, we can reinstate the home directory
manually on request.

When your account has been disabled for two or
more consecutive years we may delete your home directory and/or its archive
entirely and permanently. It will still be possible to restore it
from tape backup up for to 3 months after this, but this will
only be done under exceptional circumstances.

You will *not* recieve any warnings about this, since disabling
RUG accounts is already accompanied with warning emails.

===== Backup: =====

Tape backups are made every night of both home and project directories:

- The last 7 versions of existing files are retained up to 30 days.
- The single last version of deleted files are retained up to 60 days.

===== Note: =====

CIT offers a service for archiving research related data. For more information see:

* https://wiki.hpc.rug.nl/rdms/access/start

Sharing directories

2022-10-17T14:59:02Z

Heiko:

[[Category:misc-faq]]
If you need to share a directory between a number of people, you can use part of your home directory. 
You can also ask for a separate, appropriately-named, directory outside of your homedir, of which you will be the owner. More information on how to do that can be found [[Project Directories| here]]. 
You can grant others access by using '''Access Control Lists''', '''ACLs''' from here on. 

== How to use NFSv4 ACLs ==
You can find a detailed manual [https://www.osc.edu/resources/getting_started/howto/howto_use_nfsv4_acl here]. 
On the command-line you can give the following command to get more abbreviated usage information and some examples:
info nfs4_setfacl

== Some examples of more commonly used commands ==
To allow someone read access to a file or directory:
nfs4_setfacl -a A::'''<username>'''@rug.nl:RX '''<dir/file>'''
''Note: Use upper case '''RWX''' instead of lower case.''

It is possible to set 'default' ACLs. New files and/or sub-directories can automatically inherit these ACLs. 
To have new sub-directories inherit the ACL of it's parent:
nfs4_setfacl -a A:d:'''<username>'''@rug.nl:RX '''<dir>'''
And to have new files inherit the ACL:
nfs4_setfacl -a A:f:'''<username>'''@rug.nl:R '''<dir>'''

The ACLs can also be edited by using the editor command:
nfs4_editfacl '''<dir/file>'''
''Note: Altough you'll see different permission options, you can just use '''RWX''', this gets translated for you automatically when you save your edit.''

Sharing directories

2022-10-17T14:55:20Z

Heiko: /* How to use NFSv4 ACLs */

[[Category:misc-faq]]
If you need to share a directory between a number of people, you can use part of your home directory. 
You can also ask for a separate, appropriately-named, directory outside of your homedir, of which you will be the owner. More information on how to do that can be found [[Project Directories| here]]. 
You can grant others access by using '''Access Control Lists''', '''ACLs''' from here on. 

== How to use NFSv4 ACLs ==
You can find a detailed manual [[https://www.osc.edu/resources/getting_started/howto/howto_use_nfsv4_acl here]]. 
On the command-line you can give the following command to get more abbreviated usage information and some examples:
info nfs4_setfacl

== Some examples of more commonly used commands ==
To allow someone read access to a file or directory:
nfs4_setfacl -a A::'''<username>'''@rug.nl:RX '''<dir/file>'''
''Note: Use upper case '''RWX''' instead of lower case.''

It is possible to set 'default' ACLs. New files and/or sub-directories can automatically inherit these ACLs. 
To have new sub-directories inherit the ACL of it's parent:
nfs4_setfacl -a A:d:'''<username>'''@rug.nl:RX '''<dir>'''
And to have new files inherit the ACL:
nfs4_setfacl -a A:f:'''<username>'''@rug.nl:R '''<dir>'''

The ACLs can also be edited by using the editor command:
nfs4_editfacl '''<dir/file>'''
''Note: Altough you'll see different permission options, you can just use '''RWX''', this gets translated for you automatically when you save your edit.''

Sharing directories

2022-10-17T14:55:08Z

Heiko:

[[Category:misc-faq]]
If you need to share a directory between a number of people, you can use part of your home directory. 
You can also ask for a separate, appropriately-named, directory outside of your homedir, of which you will be the owner. More information on how to do that can be found [[Project Directories| here]]. 
You can grant others access by using '''Access Control Lists''', '''ACLs''' from here on. 

== How to use NFSv4 ACLs ==
You can find a detailed manual [[https://www.osc.edu/resources/getting_started/howto/howto_use_nfsv4_acl | here]]. 
On the command-line you can give the following command to get more abbreviated usage information and some examples:
info nfs4_setfacl

== Some examples of more commonly used commands ==
To allow someone read access to a file or directory:
nfs4_setfacl -a A::'''<username>'''@rug.nl:RX '''<dir/file>'''
''Note: Use upper case '''RWX''' instead of lower case.''

It is possible to set 'default' ACLs. New files and/or sub-directories can automatically inherit these ACLs. 
To have new sub-directories inherit the ACL of it's parent:
nfs4_setfacl -a A:d:'''<username>'''@rug.nl:RX '''<dir>'''
And to have new files inherit the ACL:
nfs4_setfacl -a A:f:'''<username>'''@rug.nl:R '''<dir>'''

The ACLs can also be edited by using the editor command:
nfs4_editfacl '''<dir/file>'''
''Note: Altough you'll see different permission options, you can just use '''RWX''', this gets translated for you automatically when you save your edit.''

Sharing directories

2022-10-17T14:52:45Z

Heiko:

[[Category:misc-faq]]
If you need to share a directory between a number of people, you can use part of your home directory. 
You can also ask for a separate, appropriately-named, directory outside of your homedir, of which you will be the owner. More information on how to do that can be found [[Project Directories| here]]. 
You can grant others access by using '''Access Control Lists''', '''ACLs''' from here on. 

== How to use NFSv4 ACLs ==
You can find a detailed manual [https://www.osc.edu/resources/getting_started/howto/howto_use_nfsv4_acl | here]. 
On the command-line you can give the following command to get more abbreviated usage information and some examples:
info nfs4_setfacl

== Some examples of more commonly used commands ==
To allow someone read access to a file or directory:
nfs4_setfacl -a A::'''<username>'''@rug.nl:RX '''<dir/file>'''
''Note: Use upper case '''RWX''' instead of lower case.''

It is possible to set 'default' ACLs. New files and/or sub-directories can automatically inherit these ACLs. 
To have new sub-directories inherit the ACL of it's parent:
nfs4_setfacl -a A:d:'''<username>'''@rug.nl:RX '''<dir>'''
And to have new files inherit the ACL:
nfs4_setfacl -a A:f:'''<username>'''@rug.nl:R '''<dir>'''

The ACLs can also be edited by using the editor command:
nfs4_editfacl '''<dir/file>'''
''Note: Altough you'll see different permission options, you can just use '''RWX''', this gets translated for you automatically when you save your edit.''

Sharing directories

2022-10-17T14:51:09Z

Heiko:

[[Category:misc-faq]]
If you need to share a directory between a number of people, you can use part of your home directory. 
You can also ask for a separate, appropriately-named, directory outside of your homedir, of which you will be the owner. More information on how to do that can be found [[Project Directories| here]]. 
You can grant others access by using '''Access Control Lists''', '''ACLs''' from here on. 

== How to use NFSv4 ACLs ==
You can find a detailed manual [https://www.osc.edu/resources/getting_started/howto/howto_use_nfsv4_acl| here]. 
On the command-line you can give the following command to get more abbreviated usage information and some examples:
info nfs4_setfacl

== Some examples of more commonly used commands ==
To allow someone read access to a file or directory:
nfs4_setfacl -a A::'''<username>'''@rug.nl:RX '''<dir/file>'''
''Note: Use upper case '''RWX''' instead of lower case.''

It is possible to set 'default' ACLs. New files and/or sub-directories can automatically inherit these ACLs. 
To have new sub-directories inherit the ACL of it's parent:
nfs4_setfacl -a A:d:'''<username>'''@rug.nl:RX '''<dir>'''
And to have new files inherit the ACL:
nfs4_setfacl -a A:f:'''<username>'''@rug.nl:R '''<dir>'''

The ACLs can also be edited by using the editor command:
nfs4_editfacl '''<dir/file>'''
''Note: Altough you'll see different permission options, you can just use '''RWX''', this gets translated for you automatically when you save your edit.''

Quota

2022-07-28T14:59:51Z

Heiko:

[[Category:home-directory-faq]]
As of october 2018, disk quota are enforced on the Home Directory Servers. That means you cannot write more data to $HOME than the allotted quotum. The server will act as if your disk is full. To reduce the chance this causes problems, there is a grace period of 7 days where you can exceed the quotum up to 10 Gb.

=== Quota info at login ===
Every time you log in, a notification message will show your current data usage and quota like this:

[[File:Screenshot-quota-info.png]]

=== Over-quota warning ===
A message like this will appear at login '''and''' every 30 minutes when your home directory usage has exceeded quota by less than 10 Gb for less than 7 days:

[[File:Screenshot-over-quota.png]]

(note that it shows when the grace period of 10 Gb extra space will end.)

=== Over-limit warning ===
When your home directory usage exceeds quota by more than 10Gb, or by less than 10 Gb but longer than 7 days, you cannot write to your home directory anymore. Among (probably) other error dialogs from other program complaining they can not write files anymore, messages like this will appear every 30 minutes:

[[File:Screenshot-over-limit.png]]

'''Q:''' How much quotum do I have?

'''A:''' As of Octobre 2018 quota will initially be set to 10 Gb more than your data usage, with a minimum of 50 Gb.

'''Q:''' What if I exceed my quotum?

'''A:''' A warning dialog will show every 30 minutes, showing the quota information. You will still be able to write to your home directory, as there is a fall-back of 10 Gb extra.

However when you exceed this fall-back limit (also called "hard limit") your programs won't be able to write anymore and will be in "disk full" condition.

The fall-back of 10 Gb extra also will expire in 7 days after first exceeding the limit. When it expires, "disk full" condition will apply as if the (hard) limit was reached.

'''Q:''' I need more space. What do I do?

'''A:''' Either delete some file you do not need anymore, or ask [mailto:lwp@rug.nl us] for more space (quotum). Generally your quotum will be increased by return, if server disk space allows. However, if you need considerably more than, say 100 Gb, we will ask you request a "project directory" and store the bulk of your files there. See: [[Project Directories]].

'''Q:''' I exceeded my quota. All my programs started complaining, and I can't work any more. I can't even log in any more.

'''A:''' That's a pity. In the worst case, press <CTRL><F2> to get to a text-mode prompt. Log in, and delete some stuff until there is free space. After you logged out, <CTRL><F7> to get back to a graphics mode screen, and perhaps reboot. You should be able to work again.

'''Q:''' Quota are a nuisance! Why do we have to have them!?!

'''A:''' If large file systems break, fixing them takes weeks. So we want small filesystems. But if one single user writes too much data, all your lwps stop working. And on a small filesystem, the risk is considerable.

'''Q:''' Why this artificial split between $HOME and /projects?

'''A:''' All your programs (shells, editors, browsers, mail, Matlab, etc. etc.) write to $HOME by default. If $HOME is full, all of those break, and some corrupt their data - silently, if you have bad luck. We '''don't''' want this for any significant number of users.
If /projects (or part of it) overflows, only the programs break that were specifically directed to it. That's still bad, but not at all as bad as all your programs failing.

Quota

2022-07-28T14:59:04Z

Heiko:

[[Category:home-directory-faq]]
As of october 2018, disk quota are enforced on the Home Directory Servers. That means you cannot write more data to $HOME than the allotted quotum. The server will act as if your disk is full. To reduce the chance this causes problems, there is a grace period of 7 days where you can exceed the quotum up to 10 Gb.

=== Quota info at login ===
Every time you log in, a notification message will show your current data usage and quota like this:

[[File:Screenshot-quota-info.png]]

=== Over-quota warning ===
A message like this will appear at login '''and''' every 30 minutes when your home directory usage has exceeded quota by less than 10 Gb for less than 7 days:

[[File:Screenshot-over-quota.png]]

(note that it shows when the grace period of 10 Gb extra space will end.)

=== Over-limit warning ===
When your home directory usage exceeds quota by more than 10Gb, or by less than 10 Gb but longer than 7 days, you cannot write to your home directory anymore. Among (probably) other error dialogs from other program complaining they can not write files anymore, messages like this will appear every 30 minutes:

[[File:Screenshot-over-limit.png]]

'''Q:''' How much quotum do I have?

'''A:''' As of Octobre 2018 quota will initially be set to 10 Gb more than your data usage, with a minimum of 50 Gb.

'''Q:''' What if I exceed my quotum?

'''A:''' A warning dialog will show every 30 minutes, showing the quota information. You will still be able to write to your home directory, as there is a fall-back of 10 Gb extra.

However when you exceed this fall-back limit (also called "hard limit") your programs won't be able to write anymore and will be in "disk full" condition.

The fall-back of 10 Gb extra also will expire in 7 days after first exceeding the limit. When it expires, "disk full" condition will apply as if the (hard) limit was reached.

'''Q:''' I need more space. What do I do?

'''A:''' Either delete some file you do not need anymore, or ask [mailto:lwp@rug.nl us] for more space (quotum). Generally your quotum will be increased by return, if server disk space allows. However, if you need considerably more than, say 100 Gb, we will ask you request a "project directory" and store the bulk of your files there. See: [[Project Directories]].

'''Q:''' I exceeded my quota. All my programs started complaining, and I can't work any more. I can't even log in any more.

'''A:''' That's a pity. In the worst case, press <CTRL><F2> to get to a text-mode prompt. Log in, and delete some stuff until there is free space. After you logged out, <CTRL><F7> to get back to a graphics mode screen, and perhaps reboot. You should be able to work again.

'''Q:''' Quota are a nuisance! Why do we have to have them!?!

'''A:''' If large file systems break, fixing them takes weeks. So we want small filesystems. But if one single user writes too much data, all your lwps stop working. And on a small filesystem, the risk is considerable.

'''Q:''' Why this artificial split between $HOME and /projects?

'''A:''' All your programs (shells, editors, browsers, mail, Matlab, etc. etc.) write to $HOME by default. If $HOME is full, all of those break, and some corrupt their data - silently, if you have bad luck. We '''don't''' want this for any significant number of users.
If /project (or part of it) overflows, only the programs break that were specifically directed to it. That's still bad, but not at all as bad as all your programs failing.

Project Directories

2022-07-28T14:58:37Z

Heiko:

[[Category:home-directory-faq]]

If you need space under /projects, contact [mailto:lwp@rug.nl us] with the following information:

* '''Name:''' What should we call that directory under /projects?
If it's just personal, we can use your account name, or (a unique abbreviation of) your own name.
* '''Size:''' How much space do you need? If we need to set up an entire new server for you, especially consider the next question.
* '''Access:''' Do we open the directory for all LWP users? Or just for you? You can let individual other users in using NFS ACLs.
* '''Pay''': Who is authorizing that use? (Cc: to supervisor, Demand Manager or whomever)
* '''Removal''': When can we discard that data? If never, consider the next question.
* '''Succession''': You are going to be the owner of that project directory. Three months after your account is revoked, we remove the data. If that should not happen, tell us whom to give it to.

Once we prepare the space for you, you can access it. Let's assume it is called 'mydir':
ls /projects/mydir

=== Sharing ===

Let's say you have a project directory, but you want to collaborate with user p111222. Here's how you give her access:
$ nfs4_setfacl -a 'A::p111222@rug.nl:RWX' /project/mydir
More detailed information on the use of '''nfs4_setfacl''' can be found [[Sharing directories| here]].

Install packages

2022-03-01T16:04:03Z

Heiko:

[[Category:software-faq]]
It is possible for users to install packages from the standard repositories we provide on their own LWP's. Students (i.e. those logging in with S-numbers) are excluded from this feature, because the PCs in the computer rooms need to diverge as little as possible and new versions of packages can cause trouble with upgrades of Ubuntu provided packages.

'''If you wish your software to be installed on all LWP's, e.g. because you need it for a course, please fill out [[Special:Contact/swreq|this software request form]].'''

We've added many extra repositories, for special packages, but they've been given a lower install priority. We've done this, so you have to deliberately install the package version you want and no accidental installs happen. You can also install anything that can be found in the ''Ubuntu Software Center''. 
----
Here are the most useful commands on the command line. 
* To search for the actual package name:
sudo apt-cache search <name of the program>
* See the available versions of a package and in what repository with what priority they can be found:
sudo apt-cache policy <package>
* Installing a package from
:1. the standard ''Ubuntu'' repositories:
sudo apt-get install <package>
:2. the extra repositories:
sudo apt-get install -t o=<origin> <package>
* With the '-t' option you can provide the <origin> of the package.
:1. If you know the repository name, the origin (o=...) can be found in the preferences file of the repository of the package:
cat /etc/apt/preferences.d/<repository_name>.pref
:2. If you don't know the repository name, you can use the following commands:
sudo apt-cache policy <package>
sudo apt-cache policy | grep -A2 <package source> | grep -o "o=.*" | cut -d"," -f1 | uniq

'''e.g.''' If you would like to install the latest version of Libreoffice on your system. It isn't available from the main repository, but it is available in one of the extra's with a lower (400) priority. (version numbers may differ)
'''sudo apt-cache policy libreoffice'''
[sudo] password for <you>:
libreoffice:
Installed: 1:3.5.7-0ubuntu5
Candidate: 1:3.5.7-0ubuntu5
Version table:
1:4.2.1-0ubuntu1~trusty 0
400 http://deb.rug.nl/ppa/mirror/ppa.launchpad.net/libreoffice/ppa/ubuntu/ precise/main amd64 Packages
*** 1:3.5.7-0ubuntu5 0
500 http://osmirror.rug.nl/ubuntu/ trusty-updates/main amd64 Packages
100 /var/lib/dpkg/status
1:3.5.4-0ubuntu1.1 0
500 http://security.ubuntu.com/ubuntu/ trusty-security/main amd64 Packages
1:3.5.2-2ubuntu1 0
500 http://osmirror.rug.nl/ubuntu/ trusty/main amd64 Packages
We can see that version 1:4.2.1 is the latest, but 1:3.5.7 is installed. 
First we'll pretend we don't know the repository file is named libreoffice.* and try to determine the origin of the package with a command:
'''sudo apt-cache policy | grep -A2 http://deb.rug.nl/ppa/mirror/ppa.launchpad.net/libreoffice/ppa/ubuntu/ | grep -o "o=.*" | cut -d"," -f1 | uniq'''
o=LP-PPA-libreoffice
If you do know the file to look in, you can do this:
'''cat /etc/apt/preferences.d/libreoffice.pref'''
# libreoffice
Explanation: : libreoffice
Package: *
Pin: release o=LP-PPA-libreoffice
Pin-Priority: 400
The "'''o=...'''" parameter is the origin, so now we can install the latest version with the addition of "'''-t o=LP-PPA-libreoffice'''" to the normal apt-get command:
'''sudo apt-get install -t o=LP-PPA-libreoffice libreoffice'''
<long list of packages and extra packages>
[y/n] y
<even longer list of stuff the system is doing>
It might ask you if you want to keep some configuration files. Usually the default (keep the config file on the system) is the best choise... unless you want to begin with a completely clean install, because of problems. When it's done, you'll have the latest version of Libreoffice installed.

Can I have root rights?

2022-03-01T15:13:54Z

Heiko:

[[Category:misc-faq]]
We strive to make the LWP such that you do not need sudo rights. In fact
you can already install all packages from all the repositories that we
have pre-configured. Example:

$ sudo apt-get install <somepackage>

For details, refer to [[install packages]].

If you need some software that is not in these repositories we have
rather that you ask us to provide it. That way we can keep track on what
is important for users and what is not.

That said you can of course install whatever you like in your [[Home directory|home directory]] or
on the local /mnt/D partition.

Examples:
$ conda create -n foo python=3.7 numpy keras
$ npm install <something>
$ pip install --user <some package> # use conda instead of pip
$ make && make install PREFIX=$HOME/local

Of course you ''can'' get sudo rights. However since in that case we do
not know anymore how your system has changed we cannot provide much more
support then just reinstalling the system.

If you tell us what it is that you want to achieve with sudo rights then
we can explain how todo that without sudo rights (or why you should not
do that).

However, if you're still convinced you need sudo rights on your system, send [mailto:lwp@rug.nl us] a request mentioning your PC's hostname and/or WKS-number. Please note that you cannot get root rights to shared PC's.

Data retention policy

2022-02-16T15:02:19Z

Heiko:

[[Category:home-directory-faq]]
== RUG account life cycle and your home directory ==

==== Summary / TL;DR: ====

When you leave the university your home directory may be deleted
permanently after 2 years (but not before).

===== Details: =====

Your general RUG account (p/s/f/g number account) is used to log
in to an LWP and is subject to the general university policy
governing these accounts. When you leave the university for any
reason your account will be disabled.

When your account has been disabled for more than 6 consecutive
months we may archive your home directory. This means it will be
compressed and put aside.

In case your account becomes enabled once again after your home
directory was archived, we can reinstate the home directory
manually on request.

When your account has been disabled for two or
more consecutive years we may delete your home directory and/or its archive
entirely and permanently. It will still be possible to restore it
from tape backup up for to 3 months after this, but this will
only be done under exceptional circumstances.

You will *not* recieve any warnings about this, since disabling
RUG accounts is already accompanied with warning emails.

===== Note: =====

CIT offers a service for archiving research realated data. For more information see:

* https://wiki.hpc.rug.nl/rdms/access/start

Data retention policy

2022-02-16T15:01:38Z

Heiko:

[[Category:home-directory-faq]]
== RUG account life cycle and your home directory ==

==== Summary / TL;DR: ====

When you leave the university your home directory may be deleted
permanently after 2 years (but not before).

===== Details: =====

Your general RUG account (p/s/f/g number account) is used to log
in to an LWP and is subject to the general university policy
governing these accounts. When you leave the university for any
reason your account will be disabled.

When your account has been disabled for more than 6 consecutive
months we may archive your home directory. This means it will be
compressed and put aside.

In case your account becomes enabled once again after your home
directory was archived, we can reinstate the home directory
manually on request.

When your account has been disabled for two or
more consecutive years we may delete your home directory and/or its archive
entirely and permanently. It will still be possible to restore it
from tape backup up for to 3 months after this, but this will
only be done under exceptional circumstances.

You will *not* recieve any warnings about this, since disabling
RUG accounts is already accompanied with warning emails.

===== Note: =====

CIT offers a service for archiving research realated data. For more information see:

* https://wiki.hpc.rug.nl/rdms/access/start

* https://www.rug.nl/society-business/centre-for-information-technology/news/rug-lid-van-irods-consortium
* https://www.rug.nl/society-business/target-fieldlab/projects-and-r-and-d/big-data-layer

Anaconda

2021-08-02T15:24:37Z

Heiko:

[[Category:anaconda-faq]]
The '''Anaconda''' Python distribution is available on LWP over and NFS mount. In order to use it on LWP instead of the locally installed Python, you need to load some environment variables into your shell.

To make Anaconda available in just your current ''bash'' session:

'''bash$''' source /opt/netapps/anaconda-lwp4/etc/profile.d/conda.sh
'''bash$''' conda activate

To have your shell startup files managed by Anaconda, so it will be available any time you start your shell:

'''bash$''' conda init

And after this, close and re-open your shell. Note that this last command also works with a select few other shells.

====Custom environments====

In order to be able to install additional packages using <code>conda install <package></code> you'll need to your own ''environment''. Such environment is stored in your home directory so it can be written to by you. By the commands above activate anaconda's default environment ''base'' and because it is stored centrally on the network it's not writable.

To create your own environment called "xmpl" (it's recommended to keep the name short):

'''bash$''' conda create --name xmpl

Activate this with:

'''bash$''' conda activate xmpl

Custom environments also allow you to use specific versions of python itself and/or module packages. For more information see [https://conda.io/projects/conda/en/latest/user-guide/getting-started.html#managing-environments the conda documentation about environments].

For more information see:

* https://en.wikipedia.org/wiki/Anaconda_(Python_distribution)
* https://docs.anaconda.com/anaconda/user-guide/

Anaconda

2021-08-02T14:43:20Z

Heiko:

[[Category:anaconda-faq]]
The '''Anaconda''' Python distribution is available on LWP over and NFS mount. In order to use it on LWP instead of the locally installed Python, you need to load some environment variables into your shell.

To make Anaconda available in just your current ''bash'' session:

'''bash$''' source /opt/netapps/anaconda-lwp4/etc/profile.d/conda.sh
'''bash$''' conda activate

To have your shell startup files managed by Anaconda, so it will be available any time you start your shell:

'''bash$''' conda init

And after this, close and re-open your shell. Note that this last command also works with a select few other shells.

====Custom environments====

In order to be able to install additional packages using <code>conda install <package></code> you'll need to your own ''environment''. Such environment is stored in your home directory so it can be written to by you. By the commands above activate anaconda's default environment ''base'' and because it is stored centrally on the network it's not writable.

To create your own environment called "xmpl" (it is recommended to keep the name short):

'''bash$''' conda create --name xmpl

Activate this with:

'''bash$''' conda activate xmpl

Custom environments also allow you to use specific versions of python itself and/or module packages. For more information see [https://conda.io/projects/conda/en/latest/user-guide/getting-started.html#managing-environments the conda documentation about environments].

For more information see:

* https://en.wikipedia.org/wiki/Anaconda_(Python_distribution)
* https://docs.anaconda.com/anaconda/user-guide/

Anaconda

2021-08-02T14:42:40Z

Heiko:

[[Category:anaconda-faq]]
The '''Anaconda''' Python distribution is available on LWP over and NFS mount. In order to use it on LWP instead of the locally installed Python, you need to load some environment variables into your shell.

To make Anaconda available in just your current ''bash'' session:

'''bash$''' source /opt/netapps/anaconda-lwp4/etc/profile.d/conda.sh # current lwp4 (Ubuntu 20.04)
'''bash$''' conda activate

To have your shell startup files managed by Anaconda, so it will be available any time you start your shell:

'''bash$''' conda init

And after this, close and re-open your shell. Note that this last command also works with a select few other shells.

====Custom environments====

In order to be able to install additional packages using <code>conda install <package></code> you'll need to your own ''environment''. Such environment is stored in your home directory so it can be written to by you. By the commands above activate anaconda's default environment ''base'' and because it is stored centrally on the network it's not writable.

To create your own environment called "xmpl" (it is recommended to keep the name short):

'''bash$''' conda create --name xmpl

Activate this with:

'''bash$''' conda activate xmpl

Custom environments also allow you to use specific versions of python itself and/or module packages. For more information see [https://conda.io/projects/conda/en/latest/user-guide/getting-started.html#managing-environments the conda documentation about environments].

For more information see:

* https://en.wikipedia.org/wiki/Anaconda_(Python_distribution)
* https://docs.anaconda.com/anaconda/user-guide/

Anaconda

2021-08-02T14:16:43Z

Heiko:

[[Category:anaconda-faq]]
The '''Anaconda''' Python distribution is available on LWP over and NFS mount. In order to use it on LWP instead of the locally installed Python, you need to load some environment variables into your shell.

To make Anaconda available in just your current ''bash'' session:

'''bash$''' source /opt/netapps/anaconda3/etc/profile.d/conda.sh # older lwp3 (Ubuntu 16.04)
'''bash$''' source /opt/netapps/anaconda-lwp4/etc/profile.d/conda.sh # current lwp4 (Ubuntu 20.04)
'''bash$''' conda activate

To have your shell startup files managed by Anaconda, so it will be available any time you start your shell:

'''bash$''' conda init

And after this, close and re-open your shell. Note that this last command also works with a select few other shells.

====Custom environments====

In order to be able to install additional packages using <code>conda install <package></code> you'll need to your own ''environment''. Such environment is stored in your home directory so it can be written to by you. By the commands above activate anaconda's default environment ''base'' and because it is stored centrally on the network it's not writable.

To create your own environment called "xmpl" (it is recommended to keep the name short):

'''bash$''' conda create --name xmpl

Activate this with:

'''bash$''' conda activate xmpl

Custom environments also allow you to use specific versions of python itself and/or module packages. For more information see [https://conda.io/projects/conda/en/latest/user-guide/getting-started.html#managing-environments the conda documentation about environments].

For more information see:

* https://en.wikipedia.org/wiki/Anaconda_(Python_distribution)
* https://docs.anaconda.com/anaconda/user-guide/

Still over quota, after deleting files

2021-07-29T07:39:24Z

Heiko:

[[Category:home-directory-faq]]
If you have deleted files, but still get notified of you disk usage being over quota, chances are the files were deleted using a GUI file manager application. Often these applications move file to some sort of "recycle bin" instead of really deleting them.

To solve, empty your "recycle bin".

If this was not the case, the following command will show the 10 largest directory (or files) in the current directory:

du -hs .[!.]* * | sort -h | tail

Note: this command may take some time to finish.

Still over quota, after deleting files

2021-07-28T10:45:49Z

Heiko:

[[Category:home-directory-faq]]
If you have deleted files, but still get notified of you disk usage being over quota, chances are the files were deleted using a GUI file manager application. Often these applications move file to some sort of "recycle bin" instead of really deleting them.

To solve, empty your "recycle bin".

If this was not the case, the following command will show the 10 largest directory (or files) in your home directory:

cd ~
du -hs .[!.]* * | sort -h | tail

Note: this command may take some time to finish.

Still over quota, after deleting files

2021-07-28T10:45:14Z

Heiko:

[[Category:home-directory-faq]]
If you have deleted files, but still get notified of you disk usage being over quota, chances are the files were deleted using a GUI file manager application. Often these applications move file to some sort of "recycle bin" instead of really deleting them.

To solve, empty your "recycle bin".

If this was not the case, the following command will show the 10 largest directory (or files) in your home directory:

cd ~
du -hs .[!.]* * | sort -h | tail

Home directory

2020-08-06T06:54:14Z

Heiko:

[[Category:home-directory-faq]]

* [[Quota]]
* [[Still over quota, after deleting files]]
* [[kerberos ticket expired | Lost access / permission denied to home directory (error: ticket expired)]]
* [[Data retention policy | Data retention policy (i.e. how long do we keep your data after you leave?) ]]

Data retention policy

2020-08-06T06:50:42Z

Heiko:

[[Category:home-directory-faq]]
== RUG account life cycle and your home directory ==

==== Summary / TL;DR: ====

When you leave the university your home directory may be deleted
permanently after 2 years (but not before).

===== Details: =====

Your general RUG account (p/s/f/g number account) is used to log
in to an LWP and is subject to the general university policy
governing these accounts. When you leave the university for any
reason your account will be disabled.

When your account has been disabled for more than 6 consecutive
months we may archive your home directory. This means it will be
compressed and put aside.

In case your account becomes enabled once again after your home
directory was archived, we can reinstate the home directory
manually on request.

When your account has been disabled for two or
more consecutive years we may delete your home directory and/or its archive
entirely and permanently. It will still be possible to restore it
from tape backup up for to 3 months after this, but this will
only be done under exceptional circumstances.

You will *not* recieve any warnings about this, since disabling
RUG accounts is already accompanied with warning emails.

===== Note: =====

CIT offers a service for archiving research realated data. For more information see:

* https://www.rug.nl/society-business/centre-for-information-technology/news/rug-lid-van-irods-consortium
* https://www.rug.nl/society-business/target-fieldlab/projects-and-r-and-d/big-data-layer
* https://wiki.hpc.rug.nl/rdms/access/start

Data retention policy

2020-06-04T07:19:52Z

Heiko:

== RUG account life cycle and your home directory ==

==== Summary / TL;DR: ====

When you leave the university your home directory may be deleted
permanently after 2 years (but not before).

===== Details: =====

Your general RUG account (p/s/f/g number account) is used to log
in to an LWP and is subject to the general university policy
governing these accounts. When you leave the university for any
reason your account will be disabled.

When your account has been disabled for more than 6 consecutive
months we may archive your home directory. This means it will be
compressed and put aside.

In case your account becomes enabled once again after your home
directory was archived, we can reinstate the home directory
manually on request.

When your account has been disabled for two or
more consecutive years we may delete your home directory and/or its archive
entirely and permanently. It will still be possible to restore it
from tape backup up for to 3 months after this, but this will
only be done under exceptional circumstances.

You will *not* recieve any warnings about this, since disabling
RUG accounts is already accompanied with warning emails.

===== Note: =====

CIT offers a service for archiving research realated data. For more information see:

* https://www.rug.nl/society-business/centre-for-information-technology/news/rug-lid-van-irods-consortium
* https://www.rug.nl/society-business/target-fieldlab/projects-and-r-and-d/big-data-layer
* https://wiki.hpc.rug.nl/rdms/access/start

Data retention policy

2020-05-26T07:44:55Z

Heiko:

== RUG account life cycle and your home directory ==

==== Summary / TL;DR: ====

When you leave the university your home directory may be deleted
permanently after 2 years (but not before).

===== Details: =====

Your general RUG account (p/s/f/g number account) is used to log
in to an LWP and is subject to the general university policy
governing these accounts. When you leave the university for any
reason your account will be disabled.

When your account has been disabled for more than 6 consecutive
months we may archive your home directory. This means it will be
compressed and put aside.

In case your account becomes enabled once again after your home
directory was archived, we can reinstate the home directory
manually on request.

When your account has been disabled uninterruptedly for two or
more years we may delete your home directory and/or its archive
entirely and permanently. It will still be possible to restore it
from tape backup up for to 3 months after this, but this will
only be done under exceptional circumstances.

You will *not* recieve any warnings about this, since disabling
RUG accounts is already accompanied with warning emails.

===== Note: =====

CIT offers a service for archiving research realated data. For more information see:

* https://www.rug.nl/society-business/centre-for-information-technology/news/rug-lid-van-irods-consortium
* https://www.rug.nl/society-business/target-fieldlab/projects-and-r-and-d/big-data-layer
* https://wiki.hpc.rug.nl/rdms/access/start

Main Page

2020-05-04T07:40:23Z

Heiko: /* Corona */

[[Category:Main]]
= LWP Wiki =
Welcome to the LWP-Wiki! For general LWP information, [http://myuniversity.rug.nl/infonet/medewerkers/ict/werkplek/werkplekken/linuxwerkplek/ the LWP main page] is the starting point. 
If you're having trouble on your LWP, our [[FAQ]] is a good place to take a look first. We might already have solved your problem once or twice before. 


== Corona ==
Staff can have [[Remote access]] to their LWP. We will keep up support as best we can.

Staff and students can have [[Remote access]] to lwp-ssh.service.rug.nl and Alfa Informatica students can also connect to karora.let.rug.nl.

When logged in a physical PC at university premises you automatically have file system permissions to put your public key in place to be able to access karora/lwp-ssh remotely from outside the RUG network. As a corona-time alternative we can put it in place for you if you send us the public key together with a photo of your ID (RUG-card, drivers license,..) from a RUG e-mail address.

== Announcements ==
{{Announcement| [[User:Heiko|Heiko]] ([[User talk:Heiko|talk]]) 11:39, 7 March 2019 (CET)| Created [[Home directory|faq page about home directory]]. Moved page about [[quota]] to this new page, and created [[kerberos ticket expired|page about kerberos tickets expiration]] }}
{{Announcement| [[User:Chris|Chris]] ([[User talk:Chris|talk]]) 17:30, 25 October 2018 (CEST)| [[Dropbox]] has stopped supporting most linux file systems. We've thought of a workaround to still access your [[Dropbox]]. You could also just switch to using our own https://unishare.nl instead. You get a lot more space and it's free.}}
{{Announcement| [[User:Heiko|Heiko]] ([[User talk:Heiko|talk]]) 17:21, 18 October 2018 (CEST)| Quota information updated. See: [[Quota]]}}
{{Announcement| [[User:Chris|Chris]] ([[User talk:Chris|talk]]) 12:31, 13 February 2018 (CET)| SPSS25 is now available.}}

== Contact ==
If you're having trouble with your LWP and the solution isn't in our [[FAQ]], contact us by using the '''support''' program on the LWP's (if possible) by entering "support" on a LWP command line or selecting it from the menu. 
For more general questions you can contact us by sending a mail to [mailto:lwp@rug.nl lwp@rug.nl].

Kerberos ticket expired

Main Page

2020-05-04T07:39:04Z

Heiko: /* Corona */

[[Category:Main]]
= LWP Wiki =
Welcome to the LWP-Wiki! For general LWP information, [http://myuniversity.rug.nl/infonet/medewerkers/ict/werkplek/werkplekken/linuxwerkplek/ the LWP main page] is the starting point. 
If you're having trouble on your LWP, our [[FAQ]] is a good place to take a look first. We might already have solved your problem once or twice before. 


== Corona ==
Staff can have [[Remote access]] to their LWP. We will keep up support as best we can.

Staff and student can have [[Remote access]] to lwp-ssh.service.rug.nl and Alfa Informactica student can also connect to karora.let.rug.nl.

When logged in a physical PC at universiy premises you're entitled to put your public key in place to be able to access karora/lwp-ssh remotely from outside the RUG network.
As a corona-time alternative we can put it in place for you if you send us the public key together with a photo of your ID (RUG-card, drivers license,..) from a RUG e-mail address.

== Announcements ==
{{Announcement| [[User:Heiko|Heiko]] ([[User talk:Heiko|talk]]) 11:39, 7 March 2019 (CET)| Created [[Home directory|faq page about home directory]]. Moved page about [[quota]] to this new page, and created [[kerberos ticket expired|page about kerberos tickets expiration]] }}
{{Announcement| [[User:Chris|Chris]] ([[User talk:Chris|talk]]) 17:30, 25 October 2018 (CEST)| [[Dropbox]] has stopped supporting most linux file systems. We've thought of a workaround to still access your [[Dropbox]]. You could also just switch to using our own https://unishare.nl instead. You get a lot more space and it's free.}}
{{Announcement| [[User:Heiko|Heiko]] ([[User talk:Heiko|talk]]) 17:21, 18 October 2018 (CEST)| Quota information updated. See: [[Quota]]}}
{{Announcement| [[User:Chris|Chris]] ([[User talk:Chris|talk]]) 12:31, 13 February 2018 (CET)| SPSS25 is now available.}}

== Contact ==
If you're having trouble with your LWP and the solution isn't in our [[FAQ]], contact us by using the '''support''' program on the LWP's (if possible) by entering "support" on a LWP command line or selecting it from the menu. 
For more general questions you can contact us by sending a mail to [mailto:lwp@rug.nl lwp@rug.nl].

Kerberos ticket expired

Main Page

2020-05-04T07:38:47Z

Heiko: /* Corona */

[[Category:Main]]
= LWP Wiki =
Welcome to the LWP-Wiki! For general LWP information, [http://myuniversity.rug.nl/infonet/medewerkers/ict/werkplek/werkplekken/linuxwerkplek/ the LWP main page] is the starting point. 
If you're having trouble on your LWP, our [[FAQ]] is a good place to take a look first. We might already have solved your problem once or twice before. 


== Corona ==
Staff can have [[Remote access]] to their LWP. We will keep up support as best we can.

Staff and student can have [[Remote access] to lwp-ssh.service.rug.nl and Alfa Informactica student can also connect to karora.let.rug.nl.

When logged in a physical PC at universiy premises you're entitled to put your public key in place to be able to access karora/lwp-ssh remotely from outside the RUG network.
As a corona-time alternative we can put it in place for you if you send us the public key together with a photo of your ID (RUG-card, drivers license,..) from a RUG e-mail address.

== Announcements ==
{{Announcement| [[User:Heiko|Heiko]] ([[User talk:Heiko|talk]]) 11:39, 7 March 2019 (CET)| Created [[Home directory|faq page about home directory]]. Moved page about [[quota]] to this new page, and created [[kerberos ticket expired|page about kerberos tickets expiration]] }}
{{Announcement| [[User:Chris|Chris]] ([[User talk:Chris|talk]]) 17:30, 25 October 2018 (CEST)| [[Dropbox]] has stopped supporting most linux file systems. We've thought of a workaround to still access your [[Dropbox]]. You could also just switch to using our own https://unishare.nl instead. You get a lot more space and it's free.}}
{{Announcement| [[User:Heiko|Heiko]] ([[User talk:Heiko|talk]]) 17:21, 18 October 2018 (CEST)| Quota information updated. See: [[Quota]]}}
{{Announcement| [[User:Chris|Chris]] ([[User talk:Chris|talk]]) 12:31, 13 February 2018 (CET)| SPSS25 is now available.}}

== Contact ==
If you're having trouble with your LWP and the solution isn't in our [[FAQ]], contact us by using the '''support''' program on the LWP's (if possible) by entering "support" on a LWP command line or selecting it from the menu. 
For more general questions you can contact us by sending a mail to [mailto:lwp@rug.nl lwp@rug.nl].

Kerberos ticket expired

Can I have root rights?

2019-11-27T08:36:59Z

Heiko:

[[Category:misc-faq]]
We strive to make the LWP such that you do not need sudo rights. In fact
you can already install all packages from all the repositories that we
have pre-configured. Example:

$ HOME=/tmp sudo apt-get install <somepackage>

For details, refer to [[install packages]].

If you need some software that is not in these repositories we have
rather that you ask us to provide it. That way we can keep track on what
is important for users and what is not.

That said you can of course install whatever you like in your [[Home directory|home directory]] or
on the local /mnt/D partition.

Examples:
$ conda create -n foo python=3.7 numpy keras
$ npm install <something>
$ pip install --user <some package> # use conda instead of pip
$ make && make install PREFIX=$HOME/local

Of course you ''can'' get sudo rights. However since in that case we do
not know anymore how your system has changed we cannot provide much more
support then just reinstalling the system.

If you tell us what it is that you want to achieve with sudo rights then
we can explain how todo that without sudo rights (or why you should not
do that).

However, if you're still convinced you need sudo rights on your system, send [mailto:lwp@rug.nl us] a request mentioning your PC's hostname and/or WKS-number. Please note that you cannot get root rights to shared PC's.

Can I have root rights?

2019-11-27T08:34:43Z

Heiko:

[[Category:misc-faq]]
We strive to make the LWP such that you do not need sudo rights. In fact
you can already install all packages from all the repositories that we
have pre-configured. Example:

$ HOME=/tmp sudo apt-get install <somepackage>

For details, refer to [[install packages]].

If you need some software that is not in these repositories we have
rather that you ask us to provide it. That way we can keep track on what
is important for users and what is not.

That said you can of course install whatever you like in your [[Home directory|home directory]] or
on the local /mnt/D partition.

Examples:
$ conda create -n foo python=3.7 numpy keras
$ npm install <something>
$ pip install --user <some package> # use conda instead of pip
$ make && make install PREFIX=$HOME/local

Of course you ''can'' get sudo rights. However since in that case we do
not know anymore how your system has changed we cannot provide much more
support then just reinstalling the system.

If you tell us what it is that you want to achieve with sudo rights then
we can explain how todo that without sudo rights (or why you should not
do that).

If you wish to get sudo rights on your system, send [mailto:lwp@rug.nl us] a request mentioning your PC's hostname and/or WKS-number. Please note that you cannot get root rights to shared PC's.

Can I have root rights?

2019-11-27T08:34:26Z

Heiko:

[[Category:misc-faq]]
We strive to make the LWP such that you do not need sudo rights. In fact
you can already install all packages from all the repositories that we
have pre-configured. Example:

$ HOME=/tmp sudo apt-get install <somepackage>

For details, refer to [[install packages]].

If you need some software that is not in these repositories we have
rather that you ask us to provide it. That way we can keep track on what
is important for users and what is not.

That said you can of course install whatever you like in your [[Home directory|home directory]] or
on the local /mnt/D partition.

Examples:
$ conda create -n foo python=3.7 numpy keras
$ npm install <something>
$ conda install --user <some package> # use conda instead of pip
$ make && make install PREFIX=$HOME/local

Of course you ''can'' get sudo rights. However since in that case we do
not know anymore how your system has changed we cannot provide much more
support then just reinstalling the system.

If you tell us what it is that you want to achieve with sudo rights then
we can explain how todo that without sudo rights (or why you should not
do that).

If you wish to get sudo rights on your system, send [mailto:lwp@rug.nl us] a request mentioning your PC's hostname and/or WKS-number. Please note that you cannot get root rights to shared PC's.

Anaconda

2019-06-05T13:27:41Z

Heiko:

Anaconda

2019-06-04T14:00:43Z

Heiko:

Anaconda

2019-06-04T13:58:05Z

Heiko: Created page with "Category:anaconda-faq The '''Anaconda''' Python distribution is available on LWP over and NFS mount. In order to use it on LWP instead of the locally installed Python, yo..."

FAQ

2019-06-04T13:41:16Z

Heiko:

[[Category:faq]]
Here we try to write down solutions to most common issues. If you think something is missing, please let [mailto:lwp@rug.nl us] know.
----
 
* [[Installing]]
* [[Remote access]]
* [[Software]]
* [[Printing]]
* [[Networking]]
* [[Graphics]]
* [[Home directory]]
* [[Docker]]
* [[Anaconda]]
* [[Miscellaneous]]

Home directory

2019-04-30T07:44:55Z

Heiko:

[[Category:home-directory-faq]]
* [[Quota]]
* [[Still over quota, after deleting files]]
* [[kerberos ticket expired | Lost access / permission denied to home directory (error: ticket expired)]]

Still over quota, after deleting files

2019-04-30T07:43:22Z

Heiko: Created page with "Category:misc-faq If you have deleted files, but still get notified of you disk usage being over quota, you probably deleted the files using a GUI file manager application..."

[[Category:misc-faq]]
If you have deleted files, but still get notified of you disk usage being over quota, you probably deleted the files using a GUI file manager application. Often these applications move file to some sort of "recycle bin" instead of really deleting them.

To solve, empty your "recycle bin".

Home directory

2019-04-30T07:38:45Z

Heiko:

[[Category:home directory faq]]
* [[Quota]]
* [[Still over quota, after deleting files]]
* [[kerberos ticket expired | Lost access / permission denied to home directory (error: ticket expired)]]