...
All the login nodes have an identical environment and can be reached with SSH (Secure Shell) protocol using the "collective" hostname:
>$ login.leonardo.cineca.it
which establishes a connection to one of the available login nodes. To connect to Leonardo you can also indicate explicitly the login nodes:
>$ login01-ext.leonardo.cineca.it
>$ login02-ext.leonardo.cineca.it it
>$ login05-ext.leonardo.cineca.it
>$ login07-ext.leonardo.cineca.it
...
The accounting (consumed budget) is active from the start of the production phase. For accounting information please consult our dedicated section.
The account_no name (or project) is important for batch executions. You need to indicate an account_no to be accounted for in the scheduler, using the flag "-A"
#SBATCH -A <account_no>name>
With the "saldo -b" command you can list all the account_no name associated with your username.
...
Since all the filesystems are based on Lustre, the usual unix command "quota" is not working. Use the local command cindata to query for disk usage and quota ("cindata -h" for help) that will be available soon.
>$ cindata
Software environment
...
If you want to use a module placed under other profiles, for example an application module, you will have to previously load the corresponding profile:
>$ module load profile/<profile name>
>$ module load <module name>
...
For listing all profiles you have loaded you can use the following command:
>$ module list
In order to detect all profiles, categories and modules available on LEONARDO, the command “modmap” is available as for the other clusters. With modmap you can see if the desired module is available and which profile you have to load to use it.
>$ modmap -m <module_name>
Spack environment
...