From 0de343187127f6a5a93602608812e60fc4092c9a Mon Sep 17 00:00:00 2001 From: Lennart Poettering Date: Wed, 3 May 2023 14:13:58 +0200 Subject: sd-daemon: add sd_pid_notify_barrier() call and use it in systemd-notify Previously we'd honour --pid= from the main notification we send, but not from the barrier. This is confusing at best. Let's fix that. --- man/sd_notify.xml | 14 ++++++++++++-- 1 file changed, 12 insertions(+), 2 deletions(-) (limited to 'man') diff --git a/man/sd_notify.xml b/man/sd_notify.xml index b82d145860..89f1729b13 100644 --- a/man/sd_notify.xml +++ b/man/sd_notify.xml @@ -24,6 +24,7 @@ sd_pid_notify_with_fds sd_pid_notifyf_with_fds sd_notify_barrier + sd_pid_notify_barrier Notify service manager about start-up completion and other service status changes @@ -83,6 +84,13 @@ int unset_environment uint64_t timeout + + + int sd_pid_notify_barrier + pid_t pid + int unset_environment + uint64_t timeout + @@ -372,8 +380,10 @@ previously sent notification messages and uses the BARRIER=1 command. It takes a relative timeout value in microseconds which is passed to ppoll2 - . A value of UINT64_MAX is interpreted as infinite timeout. - + . A value of UINT64_MAX is interpreted as infinite timeout. + + sd_pid_notify_barrier() is just like sd_notify_barrier(), + but allows specifying the originating PID for the notification message. -- cgit v1.2.1