samba.git/source3/lib/server_prefork.h, branch talloc-2.1.2

s3-prefork: Listening fds must be in non-blocking mode

2011-08-21T13:05:07+00:00

Signed-off-by: Andreas Schneider 
Signed-off-by: Simo Sorce

s3-prefork: Fix code to retire children

2011-08-21T13:05:06+00:00

We have to be more careful when retiring children. We cannot stop
accepting connections as soon as the server tells us to quit because if
max_children is reached and we still have clients connected, the server will
not be able to spawn new children until one exits. And children will not exit
until all the clients closed the connections. So we keep operating past our
recall until we have 0 connections.
Also do not try to recall children that still have >= 1 clients connected, they
couldn't anyway.
Also use messaging to warn children and not SIGHUP.

Signed-off-by: Andreas Schneider 
Signed-off-by: Simo Sorce

s3-prefork: Add parent->client messaging

2011-08-21T13:05:06+00:00

Signed-off-by: Andreas Schneider 
Signed-off-by: Simo Sorce

s3-prefork: Improve heuristics

2011-08-21T13:05:05+00:00

Signed-off-by: Andreas Schneider 
Signed-off-by: Simo Sorce

s3-prefork: Fix worker flags handling.

2011-08-21T13:05:05+00:00

We can't have a clear idea of wether the worker is IDLE or BUSY.
The only things we can tell is if it is Alive, whether it is currently
Accepting connections or wether it is Exiting soon.

Remove PF_WORKER_IDLE, PF_WORKER_BUSY and replace their use with
PF_WORKER_ALIVE. Also properly assign PF_WORKER_ACCEPTING so that
users of the API can rely on the flag.

Signed-off-by: Andreas Schneider 
Signed-off-by: Simo Sorce

s3-prefork: do not use a lock_fd, just race on accept()

2011-08-21T13:05:05+00:00

We used a lock mimicking what apache does for preforked children.
But it doesn't work properly in our case because we do not stop once a request
has been served. Clients are allowed to perform multiple requests and keep the
connection open.
This means that if we allow multiple clients per children, then a child could
take the lock and then be asked to do a long or even locking operation by a
client it already is serving. This woulkd cause the whole server to deadlock,
as the child is now busy and also holding on the lock.
Using a race on accept() by having a tevent_fd on the listening socket wait
for read events we never deadlock. At most we cause a bit of contention among
children. But in the generic case connections are much less frequent for us as
clients tend to be long lived. So the little contention we may have is not a
big deal.

Signed-off-by: Andreas Schneider 
Signed-off-by: Simo Sorce

s3-prefork: Allow better management of allowed_clients

2011-08-21T13:05:04+00:00

Signed-off-by: Andreas Schneider 
Signed-off-by: Simo Sorce

s3: Fix some typos -- Simo, please check

2011-08-10T17:40:58+00:00

s3-prefork: Pass the child a child_id

2011-08-10T16:14:05+00:00

Signed-off-by: Andreas Schneider

s3-prefork: Return tsocket_address for client and server

2011-08-10T16:14:04+00:00

Signed-off-by: Andreas Schneider