In this newsletter:
- Application License Server Maintenance by IT on Thursday, 3th June 2021, 8.00 PM to 4:00 AM 4th June
- Next maintenance session
- RCAC meeting
- Tip of the week:using nohup
- Follow us on Twitter and YouTube
- Previous Announcements
- Previous Tips
Application License Server Maintenance by IT on Thursday, 3th June 2021, 8.00 PM to 4:00 AM 4th June
Due to a scheduled maintenance of the Application License Server by IT on Thursday, 3 June 2021, 8.00 PM to 4:00 AM next day, access to the below applications will be impacted on Shaheen and Neser: Ansys, AtomistixToolKit (ATK), Converge, Eclipse, Intel Compilers, Material Studio, Mathematica, MATLAB, Tecplot and Totalview. During these maintenance windows, you may face issues with Intel at compilation and errors with the application at runtime.
Next maintenance session
We would like to announce our next maintenance session on Shaheen which will take place on Tuesday the 22nd of June. We are planning for a one full day outage (24 hours).
We will send more details and detailed timing closer to the date.
The project submission deadline for the next RCAC meeting is June 30th. Please note that the RCAC meetings are held once per month. Projects received on or before the submission deadline will be included in the agenda for the subsequent RCAC meeting.The detailed procedures, updated templates and forms are available here: https://www.hpc.kaust.edu.sa/account-applications
Tip of the week: Use “nohup” to keep processes running on Shaheen even after exiting
Sometimes, we have to run a script for a long time on the Shaheen login nodes. One example would be the installation of large third-party software. If we initiate the script directly on the Shaheen login nodes, the script will be terminated once the connection to Shaheen is interrupted for any reason. To keep processes running on Shaheen even after exiting the remote login shell, we can use the Linux command “nohup”:
nohup test.sh >& test.sh.log &
1. “test.sh” is the script you would like to run.
2. “nohup” is a command in Linux systems that keep processes running even after exiting the shell or terminal.
3. “>&” is used to redirect any standard output/errors to the log file “test.sh.log”.
4. “&” at the end of the line is used to make the command running in the background.
5. Check “test.sh.log” to see the status of the process.
Follow us on Twitter and YouTube
Follow all the latest news on HPC within the Supercomputing Lab and at KAUST, on Twitter @KAUST_HPC.
Our KSL training recordings are now available for you to browse on-demand in our KSL YouTube channel , Subscribe and hit the notification button to keep up to date with our latest material.