Running long jobs on the University Desktop
When running long jobs in Matlab and Ansys you need to use 'UniDeskLR' (University Desktop Long Running). This is because 'UniDesk' (University Desktop) sessions are subject to timeout limits. The default timeouts are:
- Disconnected session: 5 minutes
- Active session: Never
- Idle session: 3 hours
If you want to run long jobs on the University Desktop service you need to have the default timeout limits increased.
- Step 1 - ask a member of staff to complete a UniDeskLR request form.
Please note: UniDeskLR is only for Matlab and Ansys
Running a long job
Once notified that your disconnected timeout session limit has been increased
- log-in to UniDeskLR.
- Start the job you wish to run.
- Now disconnect using either the X button at the top of the session window or the 'Disconnect' option on the Start Menu.
The job will CONTINUE TO RUN until your new disconnected timeout limit has been reached. To check progress with your job simply log-in to UniDeskLR again BEFORE your disconnected session times out. Each time you log back in to a disconnected session the session timer will be reset to zero, allowing you to use your full disconnected session timeout limit once again.
DO NOT LOG OFF! If you log off from 'UniDeskLR' the job(s) will terminate!
Why not start the job and then leave the session open but minimised?
We do not recommend leaving UniDeskLR connected for extended periods if 'idle'. (The definition of idle would be with no keyboard or mouse activity.) Not only is this a potential security issue (an idle session is potentially open to outside interference), but a job could be terminated by the server when the user's idle session timeout is reached. The idle session timeout limit is given above.
PLEASE NOTE:
(i) We will meet session timeout requests wherever possible, but may have to impose certain timeout restrictions should this prove necessary for server maintenance and security.
(ii) Every effort will be made to protect disconnected sessions from disruption. However, in the case of emergency maintenance or a server failure, it may be necessary to kill disconnected sessions and their associated jobs.