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: 0) by Anonymous Coward on Monday May 30 2016, @04:49PM
I hate to say this, but pulseaudio got better once the idiot poettering moved on from it. Network manager though is a piece of crap.
I use pulseaudio because i use steam on linux and many games need it for audio. apulse doesn't cut it and I have moved on from desiring to fiddle with a system wide asound or user asound file every time i want to do something different. Play games, put this in the asound file. Listen to music, have this instead.
Poettering may be an idiot, but linux DID need a better audio manager on top of alsa drivers. When he moved on to the 'next shiny thing' others made it at least palatable. I'll keep using pulseaudio until it becomes hard linked to systemD, then i'll jump ship to whatever fork is created by similar minded people.
Also just to point out a few years ago I would have sided with you, then I was forced with a choice. Keep having to do this, eat up more of my limited time after work and find myself limited even more in what games i can and can't play. Or just bite the bullet and use it. Turns out others made it better after he left and I was just being stubborn.
(Score: 0) by Anonymous Coward on Monday May 30 2016, @06:10PM
There is apparently a way to make pulseaudio just a passthrough, without having it hog the alsa /dev files.
https://wiki.archlinux.org/index.php/PulseAudio#ALSA.2Fdmix_without_grabbing_hardware_device [archlinux.org]
(Score: 0) by Anonymous Coward on Tuesday May 31 2016, @12:49AM
Ah yes, one of the many hacks i tried that didn't work.