On Wed, May 06, 2015 at 07:10:55AM +0530, dE wrote:
> On 05/05/15 21:30, Viktor Dukhovni wrote:
> >On Tue, May 05, 2015 at 09:17:06PM +0530, dE wrote:
> >
> >>if multiple daemons listen on the single port, how is the concurrency
> >>problem handled?
> >TL;DR: Correctly.
> >
> >In detail: Multiple processes indeed share the acceptor socket,
> >but only one (otherwise) idle process at a time is monitoring it
> >for new connections. The rest (of the idle processes) are blocked
> >on a file lock, which is released by the lock holder once it accepts
> >a connection to process (and is no longer idle).
> >
>
> Thanks for sharing the detail! I would like this get documented.
This is internal implementation detail, not a public interface.
The source is available for those who want details.
All that master.cf promises is a bound on the number of processes
running for each service, and that is actually clear from master(5),
unless you're working too hard trying to guess the implementation
details (wrong), and get yourself confused.
--
Viktor.
