pub fn ready() -> Result<()>Expand description
Notify systemd that service is ready
Sends READY=1 to the notification socket.
This should be called after the service has completed initialization
and is ready to handle requests.
The sd_notify protocol is supervisor-agnostic: the message is a datagram to
whatever NOTIFY_SOCKET points at, so a direct-launch supervisor
(--daemon / no-systemd fallback, #1585) that provisions a per-child
notification endpoint gets the same post-initialization signal systemd
receives. With NOTIFY_SOCKET unset the call stays a no-op in every build.