On Tue, 2004-08-24 at 11:48 +0100, Mark Powell wrote: > On Mon, 23 Aug 2004, Matt Sergeant wrote: > > > > Now I can't do that. I previously used collapse log > > > (http://www.hjp.at/projekte/qpsmtpd/log-tools/) to collapse logs into > > > single lines for each qpsmtpd session, but this script now does not > > > work > > > as it (of course) uses the pid. > > > > PPerl tries *very* hard to emulate the calling process, including > > duplicating the pid. I don't think SpeedyCGI tries that hard. > > I've also discovered that under SpeedyCGI my authldap plugin does not > register it's handlers. It loads, but seems to do nothing at all. Even put > a couple of debug statements in sub register, which have no effect at all > under SpeedyCGI! If I go back to plain qpsmtpd or PPerl it works fine. > Cheers.
I didn't have any problems with my authldap plugin under speedyCGI. I'll attach it, but it seems to be pretty darn similar to yours. As far as the logs go, what information is provided by tcpserver that isn't shown by qpsmtpd?
auth_ldap_bind
Description: Perl program
