Russ Allbery writes:
> For comparison purposes, the *total* burden, from my upstream
> perspective, of the two options was:
> * systemd: 14 lines (8 lines of code, 6 lines of build system)
> * upstart: 12 lines (6 lines of code, 6 lines of documentation)
> Since upstart synchronization required
Ian Jackson writes:
> So overall my conclusions at this level are:
> * socket activation is an attractive implementation target for an
>upstream daemon author.
> * upstart's SIGSTOP protocol is an attractive implementation target
>for an upstream daemon author.
> * systemd's readine
Firstly: a warning note. Throughout this exercise I have been
persistently typing "upstart" when I mean "userv" and "userv" when I
mean "upstart". If something I say make no sense, please try reading
it the other way :-). (At least it gave me some extra bugs to
experience debugging...)
I have s
3 matches
Mail list logo
