John Dalbec wrote:
> I wrote a Perl script to test this. It opens an LDAP connection and
> binds to the directory. It forks a child that runs a search then sleeps
> for a while. The parent sleeps to allow the child search to complete,
> then forks a second child that runs the same search and then sleeps for
> a while. If I set up the LDAP connection unencrypted, the script runs
> fine. If I set up the LDAP connection encrypted, the second search gets
> an I/O error.
>
> I think a reasonable workaround is if Exim caches the PID along with the
> other connection information for encrypted connections and then uses the
> encrypted connection only with that PID. Does anyone have a better idea?
IIRC exim calls the tidyup-function of all lookuptypes before spawning a
new process, so this shouldn't happen as long as ldap_tidyup is
implemented correctly.
Nico
