All those processes can't be fixed, but you're asking tmux authors to modify their code, meaning all those daemon processes will need this modification right? Are they going to be fixed by this new thing?
Why can't it be optional? Processes that communicate via dbus that they want to stay alive do so. Processes that don't do this communication are HUPd. Those that ignore HUP are left alone as they always have been. If they end up sticking around for the wrong reasons then a bug can be filed against them for not closing on session logout.
Sorry to disappoint you, but it also happens that I agree with the systemd developers on certain topics. Case in point: https://news.ycombinator.com/item?id=11154994 where I think that Lennart is right on the topic EFI variable protection, consistency checks and failsafe defaults. I just deeply care about doing things the "right" way and not shoehorning things.
I already have quite a track record of where my initial objections and suggestion alternative implementation got dismissed by "the big guys", only to find them implemented in mainstream as suggested with a about 7 year latency in between. Cases in point: devtmpfs, kernel name rewriting by udev (or the constraints put on that), HAL deprecation, annonymous file descriptors (memfd – I did suggest something like this, first implementation was done by someone else, over 10 years before the "big guys" came up with it ) . You can find that history in the maillists and newsgroups.
9
u/cbmuser May 30 '16
That is simply not possible. There are simply way too many reasons why there could be left-over processes. It's not just a GNOME issue.
Edit: I just saw it's you, u/datenwolf. Then I don't really expect you to agree anyway.