I believe it's a setting in sshd. I will have to learn to run many things in tmux/screen: certainly dnf, but also all the science codes that we normally do. Actually, this will build our character: currently we kind-of depend on getting lucky if the command happens to run in background or knows to put itself in background on receivng a HUP.On Wed, Oct 05, 2016 at 04:59:57PM -0400, Przemek Klosowski wrote:Now that systemd kills processes on logout, and session timeout is required by security policies in many workplaces including mine, I fear we'll have more of those. I certainly had update sessions that involved hundreds of packages and took longer than the session timeout, whcih is often on ther order of several minutes.Please remember that we have deferred enabling the kill-processes-on-logout setting until at least F26. How is your session timeout implemented? If it's $TMOUT in bash, that shouldn't affect the _running_ command. Does it let you leave long-running processes with screen or tmux?