Slashdot Mirror

← Back to Stories (view on slashdot.org)

Systemd Starts Killing Your Background Processes By Default (blog.fefe.de)

Posted by EditorDavid on from the features-not-bugs dept.

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."

6 of 924 comments (clear)

  1. It's still hungry... by QuietLagoon · · Score: 3, Funny

    Better feed it. :)

  2. Just fix the docs... by msauve · · Score: 5, Funny

    "user sessions will be properly and improperly cleaned up after..."

    FTFY.

    --
    "National Security is the chief cause of national insecurity." - Celine's First Law
  3. Re:From a security perspective... by Peter+H.S. · · Score: 3, Funny

    The functionality remains the same, even with the new systemd defaults. But instead of using "nohup /program/ &" you use "systemd-run --user -scope /program/".

    So a slight change in syntax, not a big deal IMHO.

  4. Re:Thats demonic by Anonymous Coward · · Score: 5, Funny

    This is anti-daemonic. Systemd is committing daemon genocide while you log out and turn your back on it.

  5. Re:Sorry, Slackware is NOT an option. Nor is Gento by Anonymous Coward · · Score: 2, Funny

    Sorry, but "Devuan" sounds like a half-black, half-Puerto Rican ladyboy. I can't seriously consider using it.

  6. The problem systemd fixes by ACE209 · · Score: 3, Funny

    systemd seems to want to fix the problem that Linux is a successful server OS.

    --
    "we are all atheists about most of the gods that societies have ever believed in. Some of us just go one god further."