SIA Session Timeout Behavior on Linux

cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 
Announcements
Scheduled Maintenance: November 14–15 (starting Nov. 14 at 12:00 AM PST)
LIVEcommunity will temporarily operate in read-only mode as we prepare to welcome Idira!
Public content will remain accessible, but log-ins, posting and community interactions will be paused during this period. Thank you for your patience!
Secure Infrastructure Access
1 min read
L0 Member
No ratings

Question

When users log in via JIT, they receive the following message:

Starting a new session (session ID: xxxxxxxx-6f53-411b-9fab-594xxxxxxxxx). Once started, the session expires after 480 minutes, or 0 minutes of idle time. Your session is being recorded.

This indicates that users have up to 480 minutes (8 hours) of session time, with no idle timeout.

Could you please clarify what happens if a user is running a script when the session reaches the 480-minute timeout?

Will the script be allowed to complete, or will it be forcibly terminated when the session ends?

Answer

If the script is running interactively within the terminal, it will be terminated when the session ends after 480 minutes.
However, if the script is started in a detached manner—such as using `nohup`—it will continue running in the background even after the session is disconnected. 

Summary:

  • Interactive scripts (run directly in the terminal): Stop when the session times out.
  • Detached scripts (nohup, screen, tmux): Continue running even after the session ends.
Rate this article:
  • 608 Views
  • 0 comments
  • 0 Likes
Article Dashboard
Version history
Last Updated:
‎07-03-2025 03:19 PM
Updated by: