Bug#825394: systemd kill background processes after user logs out

As Martin Pitt said, it has been reverted already in Debian's systemd package. Here is the relevant commit: https://anonscm.debian.org/cgit/pkg-systemd/systemd.git/commit/?id=c11c9a4 Have a nice day. -- *John Brooks * On 16-06-04 07:57 PM, Brendan Halpin wrote: Please revert this. I use

Bug#825394: systemd kill background processes after user logs out

Please revert this. I use nohup to run long statistical simulations, and I have just lost 12 hours of computation. This change breaks fundamental behaviour. Brendan -- Brendan Halpin, Head, Department of Sociology, University of Limerick, Ireland Tel: w +353-61-213147 f +353-61-202569

Bug#825394: systemd kill background processes after user logs out

Just saying .. > An admin who is upgrading to a new version of the operating system > will run lots of tests before actually deploying which is > how these things are usually caught. Exactly, I do check if a screen is still up after disconnect, before pushing every update in production. I do

Bug#825394: systemd kill background processes after user logs out

If there were ever any doubt, this surely settles it: systemd truly is the pulseaudio of process control! ___ Pkg-systemd-maintainers mailing list Pkg-systemd-maintainers@lists.alioth.debian.org

Bug#825394: systemd kill background processes after user logs out

On Mon, 30 May 2016 22:19:48 +0200 John Paul Adrian Glaubitz < glaub...@physik.fu-berlin.de> wrote: > Hi! > > > don't think the right response should be to just fix it one way > > for everyone, especially not since those people in charge of hundreds > > of systems have exactly one vote, similar to

Bug#825394: systemd kill background processes after user logs out

also sprach John Paul Adrian Glaubitz [2016-05-30 23:30 +0200]: > Well, come on. Look what the usual arguments against it are: "This > has been the default for the past 30 years and now it has changed > and I am forced to change two options." This is not, by any >

Bug#825394: systemd kill background processes after user logs out

On 05/30/2016 10:52 PM, Iustin Pop wrote: > As long as they know about it. In an ideal world, yes, every such admin > would read in detail all release notes. In the real world, you've just > added more trouble for the (usually overworked) admins. An admin who is upgrading to a new version of the

Bug#825394: systemd kill background processes after user logs out

Hi! > don't think the right response should be to just fix it one way > for everyone, especially not since those people in charge of hundreds > of systems have exactly one vote, similar to those who just develop > for their own home workstation. I'm sorry, but this is a very bad argument. People

Bug#825394: systemd kill background processes after user logs out

also sprach Martin Pitt [2016-05-29 11:13 +0200]: > I believe this *is* it the expected thing to do on personal > computers. This is certainly different in environments like > universities where one often does put long-running stuff in the > background, but this doesn't appeal

Bug#825394: systemd kill background processes after user logs out

> > It may be a minority, but I'm sure it's > a significant amount of people > > Agree, I think this should remain to be considered a bug, even a critical bug. And I am sure users of screen/nohup/tmux or others "daemons" which could be affected are not a small minority, but even the majority. So

Bug#825394: systemd kill background processes after user logs out

Does setsid(1) still work? I read over this carefully, and I think the answer is yes, but I’m not sure. If it does, I’m happy. If it doesn’t, I would be annoyed. ___

Bug#825394: systemd kill background processes after user logs out

On Sun, 29 May 2016 11:46:36 +0200 Guus Sliepen wrote: > I'm sure the majority of users couldn't care less either way. What we > have to think about is: does the minority of people who really want this > feature (for example, because you want your homedir to be locked > whenever

Bug#825394: systemd kill background processes after user logs out

On Sun, May 29, 2016 at 11:13:32AM +0200, Martin Pitt wrote: > I've long wanted to enable killing leftover processes on logout. In my > world, that's what I actually expect when I log out of a computer, and > I *don't* want anything running as my user any more (which in turn > keeps my encrypted

Bug#825394: systemd kill background processes after user logs out

Michael Biebl [2016-05-27 14:09 +0200]: > The new requirement of having to enable lingering and starting > tmux/screen/nohup/ via systemd-run can certainly be considered a > nuisance and something our users are not necessarily aware of. > I share that concern. > So a NEWS.Debian entry would be the

Bug#825394: systemd kill background processes after user logs out

This new behaviour is counter-intuitive to how users expect the system to work. Among other things, it completely breaks the use of tmux/screen to save a session for another time or place, or to execute long-running tasks that don't warrant their own systemd service in a way that survives

Bug#825394: systemd kill background processes after user logs out

Yes, i sign also. New functionality is not expected behaviour. I also run long term commands under screen and logout expecting they will be active when i get back. Please, really consider reverting this back. -- Zbigniew Gralewski zbign...@gralewski.pl