Time out rserver and ssh too

[HenrikBengtsson]

Idea

There is a built-in mechanism for timing out rsession which we make use of. There is none for the rserver process itself.

What we could do is to run a monitor process in parallel that:

1. Checks of the rsession PID is running. If it still is, do nothing (or reset below timer), and sleep for a while before repeating
2. If the rsession is not running, start a timer
3. When the timer runs out after, say, 60 minutes, check if a new rsession is running. If not, then timeout the rserver process and any reverse SSH connection. This should result the rsc start process terminating.

This is useful for not leaving behind stray rsc sessions on devel nodes and elsewhere.

[HenrikBengtsson]

Implemented:

Version 0.7.0-9001

Significant changes

• The RStudio Server will automatically terminate 5 minutes after the most recent R session was terminated. An R session may be terminated either by the user (e.g. calling quit() in R), or from timing out because it has been idle for more than two hours. In other words, the default behavior is to automatically shut down everything after the user having been idle for more than 125 minutes.