SoylentNews is people
SoylentNews
The spreading of systemd continues, now actively pushed by themselves unto other projects, like tmux:
"With systemd 230 we switched to a default in which user processes started as part of a login session are terminated when the session exists (KillUserProcesses=yes).
[...] Unfortunately this means starting tmux in the usual way is not effective, because it will be killed upon logout."
It seems methods already in use (daemon, nohup) are not good for them, so handling of processes after logout has to change at their request and as how they say. They don't even engange into a discussion about the general issue, but just pop up with the "solution". And what's the "reason" all this started rolling? dbus & GNOME coders can't do a clean logout so it must be handled for them.
Just a "concidence" systemd came to the rescue and every other project like screen or wget will require changes too, or new shims like a nohup will need to be coded just in case you want to use with a non changed program. Users can probably burn all the now obsolete UNIX books. The systemd configuration becomes more like a fake option, as if you don't use it you run into the poorly programmed apps for the time being, and if they ever get fixed, the new policy has been forced into more targets.
Seen at lobsters 1 & 2 where some BSD people look pissed at best. Red Hat, please, just fork and do you own thing, leaving the rest of us in peace. Debian et al, wake up before RH signed RPMs become a hard dependency.
(Score: 2) by VLM on Tuesday May 31 2016, @12:15PM
because I have no need to display GUI programs remotely. ssh works fine for doing admin stuff on my servers.
The only exception I'm unfortunately personally aware of is mythtv-backends can only be configured via a slow painful agonizing GUI. My backend is headless and physically far away from my frontends, which sounds pretty funny out of context. Anyway life is pretty easy when you can configure the backend by networked X while standing in front of a frontend.
I've used RDP at work and to a lesser extent, at home, for headless systems that need a GUI. Pretty cool to have the same dev environment on an ipad or an android tablet or my phone or any other computer. I'll probably rig something up on the mythtv-backend so it thinks its using X locally but I'm actually talking to it over the network. In the end that would be nicer as I could mess with the backend config using one of the kids ipads while testing on the frontend.
Something I kind of like is a tricked out emacs with all the addons connected to via whatever RDP screen is nearby. Its a nice flexible development environment. It means I'm developing on a giant machine of essentially infinite resources with all the speed you'd expect yet my laptop doesn't get warm and the battery lasts quite awhile because all its really doing is shoveling from network to screen.