OK, you just hit the troll threshold (should probably have
triggered this long ago, we don;t see that here often).
I am closing this thread. Tresspassers will be punished.
Wietse
Saskia van Schagen:
> Telnet sessions work as expected. I can connect multiple times with telnet
> and since I have put a 20 second sleep in the worker threads, I don't even
> have to be fast. I connect, I get accepted, I connect with another window,
> get accepted. I print "bla", the window of the server sais : received bla
> and goes to sleep for 20 seconds. I send bla2 on the third window, the
> server window sais "received bla2".
>
> Everything as expected.
> I thought this behavior of Postfix was meant this way, so I was already
> planning to remove the multithreading part of my policy daemon, since like
> this it's just unused overhead. But I now realize that this Postfix feature
> is not "meant to be", you guy's actually think Postfix does multiple
> requests. I guess I found a bug in Postfix then. Too bad it's not taken
> seriously... :-(
>
>
>
> -----Original Message-----
> From: owner-postfix-us...@postfix.org
> [mailto:owner-postfix-us...@postfix.org] On Behalf Of Wietse Venema
> Sent: vrijdag 26 februari 2016 20:23
> To: Postfix users
> Subject: Re: Postfix & check_policyd_service no concurrent connections?
>
> Saskia van Schagen:
> > 7. While the worker thread is still working and the main thread is
> > blocking on accept(), I'm sending another e-mail.
> > 8. The main thread is still blocking on accept(), there is no new
> > client connection.
>
> That is a bug in your server. It should accept the connection as soon as the
> client makes the connection request.
>
> See Noel's suggestion for how to test this with concurrent telnet sessions.
>
> Wietse
>
>
