Systemd Starts Killing Your Background Processes By Default (blog.fefe.de)
New submitter nautsch writes: systemd changed a default value in logind.conf to "yes", which will kill all your processes, when you log out... There is already a bug-report over at debian: Debian bug tracker.
The new change means "user sessions will be properly cleaned up after," according to the changelog, "but additional steps are necessary to allow intentionally long-running processes to survive logout. To effectively allow users to run long-term tasks even if they are logged out, lingering must be enabled for them."
The new change means "user sessions will be properly cleaned up after," according to the changelog, "but additional steps are necessary to allow intentionally long-running processes to survive logout. To effectively allow users to run long-term tasks even if they are logged out, lingering must be enabled for them."
You morons all sound like a bunch of Mac users. Something from upstream does something unexpected and stupid and you idiots start making up excuses for it. It's violating expectations that have existed from the dawn of Unix quite possibly since you were even born.
You are confused.
This is Unix, not MS-DOS.
A Pirate and a Puritan look the same on a balance sheet.
So they do what everyone else has always done which is extremely sensible in multi-user environments, and because of that they get a deceiving headline on ever-decreasing-quality slashdot. If I want to read untrue clickbait I'll read yahoo.
There are literally thousands of nonsexist insults you could have and should have used. Choosing the words you did greatly weakens your own credibility.