systemd-notify(1)

.SH "NAME" systemd-notify - Notify service manager about start-up completion and other daemon status changes

.SH "SYNOPSIS"

.HP 360u

systemd-notify [OPTIONS...] [VARIABLE=VALUE...]

.HP 360u

systemd-notify --exec [OPTIONS...] [VARIABLE=VALUE...] ; -- {CMDLINE...}

.HP 360u

systemd-notify --fork [OPTIONS...] -- {CMDLINE...}

.SH "DESCRIPTION"

.PP systemd-notify may be called by service scripts to notify the invoking service manager about status changes. It can be used to send arbitrary information, encoded in an environment-block-like list of strings. Most importantly, it can be used for start-up completion notification.

.PP This is mostly just a wrapper around sd_notify() and makes this functionality available to shell scripts. For details see sd_notify(3).

.PP The command line may carry a list of environment variables to send as part of the status update.

.PP Note that systemd will refuse reception of status updates from this command unless NotifyAccess= is appropriately set for the service unit this command is called from. See systemd.service(5) for details.

.PP Note that sd_notify() notifications may be attributed to units correctly only if either the sending process is still around at the time the service manager processes the message, or if the sending process is explicitly runtime-tracked by the service manager. The latter is the case if the service manager originally forked off the process, i.e. on all processes that match NotifyAccess=main or NotifyAccess=exec. Conversely, if an auxiliary process of the unit sends an sd_notify() message and immediately exits, the service manager might not be able to properly attribute the message to the unit, and thus will ignore it, even if NotifyAccess=all is set for it. To address this systemd-notify will wait until the notification message has been processed by the service manager. When --no-block is used, this synchronization for reception of notifications is disabled, and hence the aforementioned race may occur if the invoking process is not the service manager or spawned by the service manager.

.PP systemd-notify will first attempt to invoke sd_notify() pretending to have the PID of the parent process of systemd-notify (i.e. the invoking process). This will only succeed when invoked with sufficient privileges. On failure, it will then fall back to invoking it under its own PID. This behaviour is useful in order that when the tool is invoked from a shell script the shell process — and not the systemd-notify process — appears as sender of the message, which in turn is helpful if the shell process is the main process of a service, due to the limitations of NotifyAccess=all. Use the --pid= switch to tweak this behaviour.

.SH "OPTIONS"

.PP The following options are understood:

.PP --ready

systemd-notify --fd=4 --fd=5 4</some/file 5</some/other/file

# PID=$(systemd-notify --fork -- mycommand)
...
kill "$PID"
unset PID

#!/bin/sh
mkfifo /tmp/waldo
systemd-notify --ready --status="Waiting for data..."
while : ; do


        read -r a < /tmp/waldo


        systemd-notify --status="Processing $a"


        # Do something with $a ...


        systemd-notify --status="Waiting for data..."
done