saskia101:
> Hi,
>
> I wrote a multithreading policy daemon in C to run with Postfix.
> I made a thread pool of 8 threads, waiting for a connection from Postfix.
> Everything works nice, however, there are always 7 threads idle, it's always
> just 1 thread doing some work, even though I have a busy mail server.
> Connections from Postfix come in 1 per second and I believe this is a bit
You may see one connection per second when your server closes the
connection before Postfix closes it. That's because Postfix assumes
the server has crashed, and pauses 1s before opening the connection
again.
Wietse
> low. The mother thread receives a connection from Postfix, throws it to one
> of the 8 threads and starts to listen again, so this may not even take a
> fraction of a second. But then it simply waits a full second before Postfix
> connects again with another request.
>
> I have no smtpd_client_... restrictions what so ever and am running multiple
> smtpd services (the default value). Right now it looks like a waste that I
> wrote it multithreading, since it's only using one thread at a time. Is this
> normal behavior, i.e. is Postfix trying to be nice and giving me a slow rate
> of policy requests or do I need to tell Postfix somewhere that my policy
> daemon can handle multiple connections?
>
> Hopefully somebody can give me a hint.... Thanks....
>
>
>
> --
> View this message in context:
> http://postfix.1071664.n5.nabble.com/Postfix-check-policyd-service-no-concurrent-connections-tp82254.html
> Sent from the Postfix Users mailing list archive at Nabble.com.
>
