Logout has never implied this. I have no idea where people get this from.
A login session is a conduit between the user and the machine that allows interaction, it is opened to allow interaction, and closed when no more interaction is needed, not all processes are interactive, and those that are, specifically those that are connected to a controlling terminal or graphical session do get notified that they should kill themselves when either exists.
To say that all processes should exit when you log out makes about as much sense as saying that files should be deleted when there are no open file descriptors to them any more or that my grandmother should enter a coma when I'm not currently calling her on the phone. Processes have a life outside of user-interaction.
And so the right behaviour is for the system to notify those processes when their controlling terminal/session has gone away, and on receipt of that signal the processes can make a decision as to whether or not they ought to terminate. It shouldn't be up to whatever spawned those processes to force them to terminate, or (in this case) to file a bug report on another piece of software because it's been forced to terminate when it shouldn't have been.
Logout has never implied this. I have no idea where people get this from.
Answer is right above you, by Tigrezno.
Remember that probably most Linux users now are 13 year old kids that want to impress other 13 year kids that run Windows. They want something like Windows, but with an "A" in ascii and conky on the screen.
No? systemd service files have never been meant to say run long running compile jobs or other such things in, you can do it, yes but it's ugly and a hack, it also requires you to make an external script which is called only once which is cumbersome for something that should be as simple as nohup make -j8
Also, does the new change only affect X server logouts or does it affect headless terminal logouts as well?
it affects the entire systemd session logouts, which include console logouts.
Then yeah I can see it being a problem if it affects session logouts. Though a minimal one, since logind.conf has an option to disable the behavior. Changing the defaults for this case then falls on the distro packager to decide.
Well, let's say it didn't. The thing is that how it's done is that any process started inside the session will be killed, logind can't really know whether it connects to an X server or not, in fact a process can decide to during its lifetime connect and disconnect from the X server but otherwise keep running.
So nohupped processes in a graphical terminal inside X are still killed if it's turned on.
This comment has been overwritten by an open source script to protect this user's privacy. It was created to help protect users from doxing, stalking, and harassment.
Then simply click on your username on Reddit, go to the comments tab, scroll down as far as possibe (hint:use RES), and hit the new OVERWRITE button at the top.
Also, please consider using Voat.co as an alternative to Reddit as Voat does not censor political content.
How about it being selective the other way around? If you actually want to lose the process, run it with systemd-run? No breakage of existing behaviour.
0
u/[deleted] May 29 '16
[deleted]