3 ms·

As far as I've experienced on OS X, any running process does not survive logout. Granted it's a single session, and that session is also GUI. For a GUI login,

by cmurf 10y ago

As far as I've experienced on OS X, any running process does not survive logout. Granted it's a single session, and that session is also GUI. For a GUI login, I'd expect systemd to do exactly this. Right now, wayward processes ignore or just don't grok whatever "quit" notification the DE sends, and this will cause delayed restart/shutdown for 1m30s at which point systemd kills the user session. 1m30s is too long. Whereas on GUIless server, where I use tmux, the idea I'd login, run tmux and create a session or two, detach, logout, and by logging out all my tmux sessions go poof is not expected. But even in the cited thread there's a mechanism for such processes to get a separate user session.

wtbob 10y ago
> For a GUI login, I'd expect systemd to do exactly this. Processes have always done this when they receive a hangup (HUP) signal (unless they do something else, of course, but that's up to them). > But even in the cited thread there's a mechanism for such processes to get a separate user session. That mechanism has existed for decades: it's called nohup.