[systemd-devel] Missing forked processes in 'systemctl status'

Lennart Poettering lennart at poettering.net
Wed Aug 13 10:45:28 PDT 2014


On Wed, 13.08.14 13:31, Leonid Isaev (lisaev at umail.iu.edu) wrote:

> Hi Lennart,
> 
> 	Thanks for your help on this...
> 
> On Wed, Aug 13, 2014 at 07:02:37PM +0200, Lennart Poettering wrote:
> > [...] 
> > Hmm, there's currently no nice scheme really for services that may or
> > may not fork. Maybe Type=oneshot+RemainAfterExit=yes is after all the
> > better choice there...
> > 
> > Hmm, you use KillMode=none, why that?
> 
> I don't know actually (I can't find any explanation in the git history)...
> Probably, an arbitrary choice and this line should be just dropped.
> 
> > do you know if a "systemctl daemon-reload" (or equivalent was done) that
> > might have resulted in systemd forgetting the path for one of the units?
> 
> Well, I can see this on a freshly booted machine, so I guess that's a no.

Well, maybe some script in the boot process invokes "systemctl
daemon-reload" or so? Anything in the logs?

Maybe netctl is used in your initrd, and the reexec for the transition
from initrd to the host os is the issue here?

Lennart

-- 
Lennart Poettering, Red Hat


More information about the systemd-devel mailing list