Just FYI, if you try to load up qpsmtpd thats mounted on a NFS slice with
pperl, all sorts of errors go out ;) (im sure ill get a response saying dont
run it off an nfs slice)
anything from:
pperl: failed to read 3 bytes for an OK message: Connection reset by peer
to:
pperl: failed to read 3 bytes for an OK message: Bad file descriptor
to:
pperl: resolving full pathname to script failed: No such file or directory
If you move qpsmtpd off the nfs slice, it loads fine, but i still have a
bunch of issues with it.
Interesting. I've recently discovered one weird thing in pperl where pperl tries too hard to become like the calling process, to the point of trying to set $$ to the caller's PID. If you comment out the code where it sets $$ everything starts working again. I have no idea if this will fix what you're doing.
But it does make me think there might be a call for a pperl that doesn't try quite so hard. Or a flag that says "I don't care about emulation of the caller - just give me the speedup".
Unfortunately debugging pperl is one of the hardest things I've ever had to do in my career.
Matt.
