[systemd-devel] race conditions after SIGTERM

Lennart Poettering lennart at poettering.net
Thu Aug 14 05:22:01 PDT 2014

On Sun, 27.07.14 19:53, Zbigniew Jędrzejewski-Szmek (zbyszek at in.waw.pl) wrote:

> On Sat, Jul 26, 2014 at 02:46:05PM +0200, Reindl Harald wrote:
> > after that happend a few minutes ago systemd on F19:
> > https://bugzilla.redhat.com/show_bug.cgi?id=1123557
> > 
> > since the "sleep 1" was enough over months and now "sleep 6"
> > between "systemctl stop" and rsync is also not relieable my
> > only conclusion is that systemd don't care about the still
> > running MAINPID of "type=simple" and in case of a existing
> > "ExecStopPost" the logic is correct
> Hi,
> PIDFile with Type=simple is not supported. Adding support
> would be tricky, because with Type=simple there's no obvious
> mechanism to notify systemd *when* to read the file. With
> Type=forking, when the first process exits, systemd knows
> it can read the file. It could be done with inotify maybe.

A long-standing item on the TODO list is to add a new Type=pid-file or
so that waits for a PID file to appear and uses that as indication when
a daemon is up, or dies. I figure the example above would be a good case
for this.


Lennart Poettering, Red Hat

More information about the systemd-devel mailing list