On Aug 16, 2016 4:43 PM, "Tom Lane" <t...@sss.pgh.pa.us> wrote: > > Peter Eisentraut <peter.eisentr...@2ndquadrant.com> writes: > > On 8/16/16 8:53 AM, Greg Stark wrote: > >> That's a system level change though. How would a normal user manage this? > > > Arguably, if you are a normal user, you probably shouldn't be using > > systemd to start system services under your own account. > > I'm not totally sure, but I think that the complaints were not about > systemd-driven services. (In such a case, it's almost certainly possible > to fix it by adjusting your systemd unit definition file, anyway.) > Rather, the problem arises when J. Ordinary User does > > nohup postmaster & > > and then logs out. That's certainly not much of a recipe for production > services but people have been known to do it for testing --- in fact, > that's pretty much what I do every day with test postmasters. I suppose > whenever I migrate to a recent-systemd-based distro I'm going to have to > turn off this miserable excuse for a feature. I sure hope there's a way > to do so.
I think this is a partially different issue though. They already broke the nohup approach earlier with a different change, didn't they? /Magnus
