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