Systemd Linger

A sleepy blog post about systemd linger somehow turned into a classic Linux comment-section food fight: is this a useful cleanup tool, or yet another confusing mess ordinary humans should never have to think about? The post explains a surprisingly dramatic feature in Linux: when you log out, the system can either let your apps keep running in the background or kill them off. The author says that on modern Debian, most people do not need “linger” to keep tools like screen or tmux alive, and that enabling it mostly matters if you want user programs to start before login. He also notes there’s no neat built-in way to see who has linger enabled beyond poking around in a system folder, which feels very “hidden lever behind the boiler room door.”

The comments, though, are where the real fireworks start. One reader basically summed up the anti-systemd mood in a single exhausted sigh: when things stop working the way people expect, they have to become detectives. Another called the whole setup “simply too complex,” which is basically Linux-comment-section catnip. On the other side, defenders pushed back hard, insisting Debian’s defaults haven’t broken basic screen behavior at all and that if they had, the community would have produced “great uproar and screeching.” And then came the scope-creep accusation: one commenter said this is exactly the kind of feature expansion that fuels all the hand-wringing around systemd. In other words: one side sees helpful housekeeping, the other sees a digital landlord throwing your stuff onto the curb.