[Izkata]

> Systemd the init service is excellent.

When it's not actively going against decades of convention and breaking solid programs everyone has used forever: https://superuser.com/questions/1372963/how-do-i-keep-system...

(screen was also affected, not just tmux)

I'm not sure if it was linked from there, but somewhere in the discussions the systemd devs' recommended fix was for screen/tmux/anything else affected to add some systemd integration for their new API.

As far as I'm aware the complaints about this stopped only because distros override the setting, while it's still the default for stock systemd.

[ecnahc515]

I've been impacted by this particular "issue" and while it's changing the way "decades of convention" it's not really a bad thing imo. Running things via screen and tmux as a solution to background tasks has always been a huge hack imo. Not only that but the alternative approaches with nohup and disown also have their own issues. Imo it's actually pretty reasonable to need to work work the OS service manager to run background tasks, even with tmux and screen.

[Izkata]

Those were just the most prominent things, which were immediately noticed because it's completely normal to leave them open remotely to maintain context for something and quickly pick it back up when reconnecting. It's kind of their whole purpose. But the change affected everything, including for example the "daemonize" program.

[happymellon]

I think this points out my reasoning perfectly.

Systemd the init didn't do any of this. This is systemd-logind that is doing this.

Conflating multiple projects with the same name is a terrible idea.