Dave Reisner writes:
On Thu, Jun 07, 2012 at 08:41:54AM -0400, Sam Varshavchik wrote:
This is wrong. ExecReload should not cause the process to change PIDs.
Not that this was ever allowed, but the below commit is was causes the
SIGKILL behavior you're seeing:
http://cgit.freedesktop.org/system
On 06/07/2012 12:41 PM, Sam Varshavchik wrote:
The service file has Type=Forking and RemainAfterExit=true.
Hmm which unit file is this?
You dont use RemainAfterExit=true with Type=forking
JBG
___
systemd-devel mailing list
[email protected]
On Thu, Jun 07, 2012 at 08:41:54AM -0400, Sam Varshavchik wrote:
> After going from F16 to F17, going from systemd 37 to systemd 44,
> seemingly, my ExecReload broke.
>
> Using strace, my process is getting SIGKILLed. I suspect this is
> systemd's doing, and I would like to confirm my suspicions.
Sam Varshavchik writes:
Assuming that my guess is true, and that ExecReload's behavior in systemd
has changed, how should I configure something like this, then, for
ExecReload to spawn off a child process to take the existing child process's
place?
One last detail I forgot. The background
After going from F16 to F17, going from systemd 37 to systemd 44, seemingly,
my ExecReload broke.
Using strace, my process is getting SIGKILLed. I suspect this is systemd's
doing, and I would like to confirm my suspicions.
The service file has Type=Forking and RemainAfterExit=true.
The pro
