Systemd 230 Is Upsetting Some Over Its KillUserProcess Setting

[phoronix]

Phoronix: Systemd 230 Is Upsetting Some Over Its KillUserProcess Setting

Systemd 230 was released just last week and it has taken heat not only for opening up FBDEV to potential security issues, which already reverted, but also for changing the default behavior of user processes...

http://www.phoronix.com/scan.php?page=news_item&px=systemd-230-KillUserProcesses

[davidbepo]

like some systemd haters said its starting to mess things, which is unfortunate cause it speedups boot process and has some advantages

the setting is logical but it should have a whitelist

[caligula]

like some systemd haters said its starting to mess things, which is unfortunate cause it speedups boot process and has some advantages

the setting is logical but it should have a whitelist

Just for the record, the alternatives aren't that slow. My Raspberry Pi 1 boots almost as fast as my Haswell system although it uses runit as init.

[c117152]

What are they complaining about? It's a completely reasonable default to kill off processes on logoff.

If package maintainers would have done the right thing to begin with and packaged the services' unit files as separate $PACKAGE-systemd-unit packages, they could have updated everything without forcing everyone to download all the binaries again.

But no... They had to force systemd down everyone's throats by putting everything together like a big blob.

And you know what's the worst part? I'm was a systemd advocate and package maintainer and despite this I've voiced this very thoughts and concerns on IRC and pushed for following this very policy, but never got the votes since people got partisan about this and camped on PRO and CON systemd sides so the correct technical steps were never taken.

Well, screw them. I've switched to Guix and NixOS. With Shepherd in the first, and systemd in the other, stuff is getting done the right way in both. Let the Debians and Fedoras rot in their politics. The people who actually care about doing things the right way are off to greener pastures.

[Steffo]

With "loginctl enable-linger" everything works as expected. See https://www.freedesktop.org/software/systemd/man/systemd-run.html#Examples
To me, this new default behaviour is the right choice, because I am a desktop user and annoyed about processes which don't shut down even within 90 seconds!

[pal666]

screen and ssh-agent just have to be started as systemd services. and btw, gnome-session acts as ssh-agent and it always exits on logout

I've voiced this very thoughts and concerns on IRC and pushed for following this very policy, but never got the votes

it clearly says you are marginal

[davidbepo]

Just for the record, the alternatives aren't that slow. My Raspberry Pi 1 boots almost as fast as my Haswell system although it uses runit as init.

i was referring to upstart or sysvinit

i havent tried nor do i know about the architecture of openrc or runit

[pal666]

Just for the record, the alternatives aren't that slow. My Raspberry Pi 1 boots almost as fast as my Haswell system although it uses runit as init.

do your "alternatives" run user sessions (which are the point of subject article)?

[c117152]

it clearly says you are marginal

Thanks. Remembering how those flame wars were conducted, I take pride in not taking clear sides.

Though to be fair, packaging was always a politically loaded subject. By then, a lot of people already moved to Arch and other distributions to escape the corporate interests of server farms and Red Hat vs Ubuntu turf wars. I simply stuck around longer since I was part of the machine.

[Naib]

do your "alternatives" run user sessions (which are the point of subject article)?

the "alternatives" are init system NOT system dictators.