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:&#x2F;&#x2F;www.reddit.com&#x2F;r&#x2F;programming&#x2F;comments&#x2F;4ldewx&#x2F;systemd_kills_screen_and_tmux_by_default_on_logout&#x2F;" rel="nofollow">https:&#x2F;&#x2F;www.reddit.com&#x2F;r&#x2F;programming&#x2F;comments&#x2F;4ldewx&#x2F;systemd...</a><p>Namely that systemd doesn&#x27;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 &quot;screen&quot; whose entire raison d&#x27;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 &quot;KillUserProcesses=no&quot; in logind.conf &amp;co. - have so far failed.<p>I don&#x27;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: &quot;this is the right way, I don&#x27;t care about tradition or protecting &#x27;incorrect&#x27; usage.&quot;</i>