Re: [systemd-devel] Child of daemon sending SIGCHLD to systemd

2020-07-01 Thread Ian Pilcher
On 7/1/20 3:47 AM, Mantas Mikulėnas wrote: systemd doesn't explicitly reparent processes; the kernel just always reparents processes to pid 1 when the previous parent no longer exists. Overall, pid 1 is a legitimate recipient of SIGCHLD regardless of which init system is being used. In this c

Re: [systemd-devel] Child of daemon sending SIGCHLD to systemd

2020-07-01 Thread Mantas Mikulėnas
On Wed, Jul 1, 2020 at 3:03 AM Ian Pilcher wrote: > On 6/30/20 4:18 AM, Lennart Poettering wrote: > > > > Maybe it double forks or forks a child off (callout script?) that > > double forks somewhere? > > > > I don't know your software, it's probably best to ping the authors of > > it about this,

Re: [systemd-devel] Child of daemon sending SIGCHLD to systemd

2020-06-30 Thread Ian Pilcher
On 6/30/20 4:18 AM, Lennart Poettering wrote: Maybe it double forks or forks a child off (callout script?) that double forks somewhere? I don't know your software, it's probably best to ping the authors of it about this, they should know what their software does. LOL! I am the author. So I

Re: [systemd-devel] Child of daemon sending SIGCHLD to systemd

2020-06-30 Thread Lennart Poettering
On Mo, 29.06.20 12:19, Ian Pilcher (arequip...@gmail.com) wrote: > I originally posted a variation of the question on the SELinux mailing > list, but the more I look at this the more I realize that it really > isn't a SELinux questions. I'm not really sure that it's a systemd > question either, b

Re: [systemd-devel] Child of daemon sending SIGCHLD to systemd

2020-06-29 Thread Vito Caputo
On Mon, Jun 29, 2020 at 02:11:06PM -0500, Ian Pilcher wrote: > On 6/29/20 2:00 PM, Vito Caputo wrote: > > I don't know about freecusd, but if it uses a fire-and-forget approach > > to launching helpers, as in it double-forks, so it doesn't need to > > bother with asynchronously reaping zombies, the

Re: [systemd-devel] Child of daemon sending SIGCHLD to systemd

2020-06-29 Thread Ian Pilcher
On 6/29/20 2:00 PM, Vito Caputo wrote: I don't know about freecusd, but if it uses a fire-and-forget approach to launching helpers, as in it double-forks, so it doesn't need to bother with asynchronously reaping zombies, then the second fork becomes a child of init. That results in the second fo

Re: [systemd-devel] Child of daemon sending SIGCHLD to systemd

2020-06-29 Thread Vito Caputo
On Mon, Jun 29, 2020 at 12:19:54PM -0500, Ian Pilcher wrote: > > > Is there a circumstance in which the grandchild (freecusd_smart_helper) > would send SIGCHLD to systemd while its parent is still running? > I don't know about freecusd, but if it uses a fire-and-forget approach to launching hel

[systemd-devel] Child of daemon sending SIGCHLD to systemd

2020-06-29 Thread Ian Pilcher
I originally posted a variation of the question on the SELinux mailing list, but the more I look at this the more I realize that it really isn't a SELinux questions. I'm not really sure that it's a systemd question either, but it definitely falls into the area of Linux process management, so I'm