upstart socket activation

[Lennart Poettering]

On Wed, 16.03.11 15:57, Scott James Remnant (scott at netsplit.com) wrote:

> 
> On Wed, Mar 16, 2011 at 3:54 PM, Lennart Poettering
> <mzhcfgneg at 0pointer.de> wrote:
> > On Wed, 16.03.11 06:13, Clint Byrum (clint at ubuntu.com) wrote:
> >
> >>
> >> On Wed, 2011-03-16 at 11:17 +0100, Steffen Barszus wrote:
> >> > I have read about socket activation feature, and i'm quite
> >> > confused now and would like to have a definitive answer.
> >> >
> >> > Is the socket activation:
> >> > a) xinetd like: start the provider of the socket, once the socket is
> >> > accessed ? Anything special done until the provider is available ?
> >>
> >> Yes its like xinetd, though instead of an accepted socket being
> >> available, you're getting a listening socket with a connection ready to
> >> accept, so most daemons (no daemons?) won't support this just yet.
> >
> > BTW, what's the API for this looking like? How are the fd's passed to
> > the daemon?
> >
> >From the bridge process to the init daemon?
> 
> D-Bus FD passing.

Care to elaborate? Can I have a look at the API somewhere? Is there
example code for the daemon side available?

Can you explain why the $LISTEN_FDS logic systemd uses is not
acceptable to Upstart?

Lennart

-- 
Lennart Poettering - Red Hat, Inc.