Benjamin Robin 9de009a9f5 systemd-notify: Always pass a valid pid to sd_pid_notify
If the option --pid was used, take the pid from this option, unless take
the parend pid. Using 0 as pid (ucred of systemd-notify) will result 99% of the
time in a failure with this error: "Cannot find unit for notify message of PID"

Shouldn't we use always the ppid, since the MAINPID is something else ?

Signed-off-by: Benjamin Robin <dev@benjarobin.fr>
2015-09-20 04:02:20 +02:00
2015-06-15 00:13:43 +03:00
2015-07-06 17:47:38 +02:00
2015-09-18 14:28:16 +02:00
2015-09-15 00:20:51 +02:00
2015-08-09 18:07:55 +02:00
2015-07-27 20:15:34 +02:00
2015-08-31 18:12:37 +02:00
2015-08-05 21:02:41 -04:00
2014-02-18 02:51:47 +01:00
2015-06-03 00:22:53 +02:00
2014-06-04 15:41:10 -04:00
2015-07-27 20:15:34 +02:00
2015-09-08 13:31:57 +02:00
2015-09-11 18:28:03 +02:00

systemd - System and Service Manager

Build Status
Coverity Scan Status

Details

  • General information about systemd can be found in the systemd Wiki
  • Information about build requirements are provided in the README file
S
Description
systemd patched fork
Readme
409 MiB
Languages
C 88.5%
Shell 5.7%
Python 4.6%
Meson 1.1%