Home
last modified time | relevance | path

Searched refs:sd_notify (Results 1 – 20 of 20) sorted by relevance

/systemd-251/src/test/
Dtest-daemon.c32 sd_notify(0, in main()
36 sd_notify(0, in main()
41 sd_notify(0, in main()
46 sd_notify(0, in main()
51 sd_notify(0, in main()
/systemd-251/src/shared/
Ddaemon-util.h13 (void) sd_notify(false, start); in notify_start()
21 (void) sd_notify(false, *p); in notify_on_cleanup()
Dbus-util.c129 sd_notify(false, "STOPPING=1"); in bus_event_loop_with_idle()
/systemd-251/src/portable/
Dportabled.c157 r = sd_notify(false, NOTIFY_READY); in run()
163 (void) sd_notify(false, NOTIFY_STOPPING); in run()
/systemd-251/src/machine/
Dmachined.c353 r = sd_notify(false, NOTIFY_READY); in run()
359 (void) sd_notify(false, NOTIFY_STOPPING); in run()
/systemd-251/src/systemd/
Dsd-daemon.h246 int sd_notify(int unset_environment, const char *state);
/systemd-251/src/journal-remote/
Djournal-upload-journal.c248 sd_notify(false, "WATCHDOG=1"); in check_update_watchdog()
/systemd-251/src/rfkill/
Drfkill.c317 r = sd_notify(false, "READY=1"); in run()
/systemd-251/docs/
DPORTABILITY_AND_STABILITY.md18 …y `$NOTIFY_SOCKET`**, as documented in [sd_notify(3)](https://www.freedesktop.org/software/systemd…
97 | [$NOTIFY_SOCKET Daemon Notifications](https://www.freedesktop.org/software/systemd/man/sd_notify.…
DCONTAINER_INTERFACE.md193 using the usual `sd_notify()` protocol that is also used when a service
250 3. The `/run/host/notify` path is a good choice to place the `sd_notify()`
/systemd-251/src/udev/
Dudevd.c322 sd_notify(false, in manager_exit()
353 sd_notify(false, in manager_reload()
2075 sd_notify(false, in main_loop()
/systemd-251/src/libsystemd/
Dlibsystemd.sym75 sd_notify;
/systemd-251/src/libsystemd/sd-daemon/
Dsd-daemon.c578 _public_ int sd_notify(int unset_environment, const char *state) { in sd_notify() function
/systemd-251/man/rules/
Dmeson.build783 ['sd_notify',
/systemd-251/
DTODO232 become the official way to reload, and daemon has to respond with sd_notify()
246 * beef up sd_notify() to support AV_VSOCK in $NOTIFY_SOCKET, so that VM
256 appropriate qemu cmdline. That way qemu payloads could talk sd_notify()
338 container. i.e send an sd_notify() from payload to container manager once
620 - add sd_notify() command for flushing out creds not needed anymore
942 * add proper dbus APIs for the various sd_notify() commands, such as MAINPID=1
1104 * PID 1 should send out sd_notify("WATCHDOG=1") messages (for usage in the --user mode, and when ru…
DNEWS679 is shown, the most recent sd_notify() STATUS= text is now shown as
2790 using sd_notify(). The container manager now uses the
3681 API. The call will block until all previously sent sd_notify()
3690 track of, using the sd_notify() mechanism, a new parameter FDPOLL=0
4493 sd_notify() to trigger an immediate "watchdog missed" event, and thus
6644 * The sd_notify() protocol gained support for a new operation: with
6662 * The sd_notify() protocol can now with EXTEND_TIMEOUT_USEC=microsecond
6842 * When a service sends RELOAD=1 via sd_notify() and reload propagation
7902 sending a WATCHDOG_USEC= message via sd_notify().
8697 parallelize boot-up, as logging and sd_notify() are unlikely
[all …]
/systemd-251/src/timesync/
Dtimesyncd-manager.c916 (void) sd_notify(false, "STATUS=Idle."); in manager_disconnect()
/systemd-251/src/nspawn/
Dnspawn.c4267 r = sd_notify(false, "READY=1\n"); in nspawn_dispatch_notify_fd()
5159 r = sd_notify(false, "READY=1\n"); in run_container()
5858 (void) sd_notify(false, in run()
/systemd-251/src/core/
Dmanager.c3555 r = sd_notify(false, in user_manager_send_ready()
3572 r = sd_notify(false, in manager_send_ready()
/systemd-251/src/libsystemd/sd-event/
Dsd-event.c3802 sd_notify(false, "WATCHDOG=1"); in process_watchdog()
4379 sd_notify(false, "WATCHDOG=1"); in sd_event_set_watchdog()