On Wed, Nov 27, 2013 at 2:32 AM, Lennart Poettering <lenn...@poettering.net> wrote: > Well, but EPOLLET only works correctly if each time an event is > triggered we dispatch *all* possibly queued events on the fd, until > EAGAIN is read again. But we don't do that, heck, if Listen=no is used > we don''t even read a single incoming connection of the scket, we leave > that to the daemon we spawn, but we cannot trust that. So, I don't get > what EPOLLET is supposed to do good here?
I should have more selectively quoted before answering. I was only trying to answer why we'd continue having poll for the socket fds after queuing the initial service. I was not trying to suggest EPOLLET is appropriate for the goal of lazy "distribute" process pool expansion. You've clearly correct about that. _______________________________________________ systemd-devel mailing list systemd-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/systemd-devel