Anthony Towns <a...@erisian.com.au> writes: > On Jan 5, 2014 10:40 AM, "Russ Allbery" <r...@debian.org> wrote: >> Anthony Towns <a...@erisian.com.au> writes:
>>> How hard would it be to write an external wrapper that converts the >>> systemd style socket activation to the SIGSTOP protocol (for upstart >>> invoking a systemd compatible daemon)? > On second thoughts, I think I meant this the other way around - systemd > invoking an upstart compatible daemon, since it seems like upstart is > more likely to support the systemd socket activation protocol than > systemd is to support upstart's SIGSTOP protocol. This, sadly, is slightly harder, since you can't use this hack: >> The wrapper could fork and then exec the daemon in the *parent*, and >> have the *child* listen for the notification message and then >> kill(SIGSTOP) its parent and immediately exit. I wonder if that would >> actually work.... because the child can't waitpid its parent and get notified when the parent stops. So the compatibility wrapper would have to stick around for the lifetime of the daemon and pass signals and the like, and I'm not sure what gotchas would be involved in that. But it's probably doable. -- Russ Allbery (r...@debian.org) <http://www.eyrie.org/~eagle/> -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
