Uoti Urpala writes ("Bug#727708: systemd socket activation protocol rationale"):
> On Sat, 2013-12-14 at 21:45 +, Ian Jackson wrote:
> > Why do only some of the environment variables start "SD_" ?
> > We have LISTEN_PID and LISTEN_FDS but SD_LISTEN_FDS_STAR
On Sat, Dec 14, 2013 at 11:53:42PM +0100, Michael Stapelberg wrote:
> Ian Jackson writes:
> > I think it would be good, regardless of what the TC decides on the
> > init system question for Debian, for systemd and upstart to converge
> > on a single reasonable protocol.
> Helmut Grohne has done so
Hi Ian,
[still sending this after Uoti’s reply, because my version has some more
detail]
Ian Jackson writes:
> Why do only some of the environment variables start "SD_" ?
> We have LISTEN_PID and LISTEN_FDS but SD_LISTEN_FDS_START.
SD_LISTEN_FDS_START is a #define from sd-daemon.h, not an enviro
On Sat, 2013-12-14 at 21:45 +, Ian Jackson wrote:
> I've just been reading sd_listen_fds(3). It's vaguely similar to
> upstart's socket activation protocol. It supports multiple sockets
> (which is obviously important).
>
> But I have a few questions about the details:
>
> Why do only some
I've just been reading sd_listen_fds(3). It's vaguely similar to
upstart's socket activation protocol. It supports multiple sockets
(which is obviously important).
But I have a few questions about the details:
Why do only some of the environment variables start "SD_" ?
We have LISTEN_PID and LI
5 matches
Mail list logo
