Systemd, ten years later: a historical and technical retrospective
As a somewhat dilettante and casual home sysadmin (currently) I was messing around with screen on a box downstairs and ran into this:<p><a href="https://www.reddit.com/r/programming/comments/4ldewx/systemd_kills_screen_and_tmux_by_default_on_logout/" rel="nofollow">https://www.reddit.com/r/programming/comments/4ldewx/systemd...</a><p>Namely that systemd doesn't allow persistent processes started from the shell by default, preferring to terminate them when the user logs out.<p>This would include processes like "screen" whose entire raison d'etre is to persist after the user logs out. (Well, it has other uses, but this is the main one IMO.)<p>The stated workarounds - fiddling with some options like "KillUserProcesses=no" in logind.conf &co. - have so far failed.<p>I don't know whether this situation is a problem with systemd or the distro, but it seems very much a problem with the culture summarised by the top commenter in the above thread, of (paraphrasing) <i>glibly breaking existing workflows then casually brushing away criticism with arguments often boiling down to: "this is the right way, I don't care about tradition or protecting 'incorrect' usage."</i>