If you are a faculty member or student at the participating universities, you may request a login account on the DAS-2 system by sending mail to firstname.lastname@example.org. This adress should also be contacted in case you cannot login to DAS-2 with your previous DAS-1 user id.
The DAS-2 clusters do not form one seamless whole. In particular, the password administration is done per site: the master copy of the password files is at fs0.das2.cs.vu.nl, and users should only change their password there. The password files at the other sites will be regularly updated with the version at the master site.
The file systems at different sites are completely separate, so it will be necessary to transfer the files between the home directories manually (e.g., by means of scp), or by using Grid software that does this transparently for you.
Besides the home directories, the directory /var/scratch of the file server is also mounted on each DAS-2 node. You can use the subdirectory /var/scratch/<userid> for temporary bulk storage during or between jobs. In case you need space for temporary files on each node separately, you can use /var/tmp/<userid>. Please empty /var/scratch/<userid> and /var/tmp/<userid> when you no longer need the space.
Problem reports, e.g., missing software or documentation or apparent hardware failures, should be sent to email@example.com.
For account related support (e.g., if you ran out of diskquota or you forgot your password) please send mail to firstname.lastname@example.org.
Access to the DAS-2 is possible by logging in to the
DAS-2 fileserver at one of the participating sites using
ssh (secure shell). One of the advantages of ssh over telnet
or rlogin is that it does not send sensitive password information
over the network in plaintext format.
Users will typically login to one of the DAS-2 file servers, develop software there, and start the parallel applications on a subset of the compute nodes. To avoid people getting in each other's way on the compute nodes, every DAS-2 user is required to use the cluster startup and reservation commands described in this section.