forwarding to systemd-devel for discussion
---------- Forwarded message ---------- From: Ian Jackson <[email protected]> Date: Sat, Dec 14, 2013 at 1:05 PM Subject: [Pkg-systemd-maintainers] Bug#732157: Want SIGSTOP-style daemon/service readiness notification To: [email protected] Package: systemd Version: 204-5 Severity: wishlist It would be nice if systemd could implement the service supervisor side of the service readiness protocol that upstart calls "expect stop": The service doesn't fork, and when considers itself ready it raises SIGSTOP. The supervisor can observe this via the usual mechanisms, being the service's parent, and when it occurs it sends the service CONT and starts whatever was waiting for readiness. The sd_notify(3) protocol is just about tolerable, and it is good that it's documented, but it is quite unattractive for a daemon author: Either they have to add a build- and runtime- dependency on a systemd-specific library, or they have to reimplement a fairly tedious piece of socket code. For a daemon author, raise(SIGSTOP) is lovely and simple. I guess this would be a new "Type" (but I'm still halfway through the docs so no expert). Ian. _______________________________________________ Pkg-systemd-maintainers mailing list [email protected] http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-systemd-maintainers _______________________________________________ systemd-devel mailing list [email protected] http://lists.freedesktop.org/mailman/listinfo/systemd-devel
