This is an old revision of the document!
The standard Lorentz Institute workstation runs the GNU/Linux operating system (Fedora 25), 64-bit. The workstations are configured to host a variety of scientific and non-scientific software to maximize your productivity. You are allowed to install and/or build packages locally (directories to which you have access), but for system-wide installations you must file a request through our helpdesk application.
Although the workstations might differ in their hardware specifications, they are set so that you can switch from one to the other flawlessly. For instance, the home directories are not local to a particular machine, but they are `mounted' as a network file system. One of the immediate advantages of this configuration is that you can access you home files upon login no matter the workstation you are working on. On the other hand, having the home directories mounted over the network can result in problems if the home file system is not accessible, such as in the event of a network disruption.
The home disk is `automounted' on boot.
$ df /home Filesystem 1K-blocks Used Available Use% Mounted on home:/export/home 3170555392 1260111360 1910444032 40% /home
Each user has an allocated quota on the home disk depending on their role within the Lorentz Institute. The standard quota is 4GB, nonetheless it is possible to request extra space. To check your quota settings type
$ quota -s Disk quotas for user xxxxxx (uid 999x99): Filesystem space quota limit grace files quota limit grace home:/export/home 12344K 4786M 4883M 279 0 0
TIP: Regularly check that you are below your assigned quota. Your workstation will stop working correctly if softwares cannot write temporary files in your home folder any more.
To compile a list of the ten largest files in a directory execute
du -h /home/your_username/some_directory | sort -rh | head
Then clean up responsibly.
Each workstation could have one or more local hard disks among which one is used to host the operating system files. The remaining space can be used to store relatively large files and will be accessible through the mount points /data1, /data2,…,/data[n].
$ df /data[0-9]* Filesystem 1K-blocks Used Available Use% Mounted on /dev/sda7 1838137644 67915552 1676827048 4% /data1 /dev/md0 1922599800 27092644 1797821652 2% /data2
Usually /data2 is configured as the mount point of a RAID[1|5] stack, meaning that data in it have a certain level of redundancy which can protect against disk failures. Note however, that storing all of your data on /data2 will not prevent loss if all disks in the array configuration `die' and/or your computer tower gets destroyed by a fire or any other disastrous event.
To check if a RAID configuration is used on your workstation type
$ cat /proc/mdstat Personalities : unused devices: <none>
In the example above there are no disks arranged in a RAID.
The Lorentz workstations come with a set of shell interpreters pre-installed. Your login shell can be chosen upon registration of your Lorentz account (HL 409b). Alternatively, it is possible to use a different shell interpreter at any time by just invoking it, e.g.
Partitions named data1,…,datan are usually network-shared among all the Lorentz Institute workstations. You can access /data1 on a machine called bingo via /net/bingo/data1. More generally, the pattern to access a data disk on a Lorentz machine is
Note that in the example above <workstation> can either be bingo or bingo.lorentz.leidenuniv.nl with no difference. TIP: The `mounting' of these network file systems is managed by autofs. This means that those disks will not be mounted until there is an attempt to access them, for instance by contents listing (ls) or change of working directory (cd).
A variety of compilers and libraries are available on your workstation. Please refer to the following manual pages for more info.
Here we only give a summary of useful commands.
# shows which environment modules are available module avail # load module module load <modulename> # unload module module unload <modulename>
NOTE: If sfinx was not installed under your account, you might see less modules on your workstation. In this case install sfinx paying attention to the fact that your .bashrc, .cshrc, etc… will be overwritten!
Should you need assistance operating your workstation, please do not hesitate to request help via our helpdesk application. You can also visit our offices in the Huygens Laboratory Room 409b at any time during working hours.
Comments and suggestions to improve this guide are welcome.