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. ----- Original Message ----- From: "Matt Sergeant" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Cc: "qpsmtpd ML" <[EMAIL PROTECTED]> Sent: Tuesday, March 09, 2004 4:56 PM Subject: Re: PPerl usage > On 9 Mar 2004, at 21:49, [EMAIL PROTECTED] wrote: > > > On Tue, 9 Mar 2004, Robert Spier wrote: > > > >>> Apart from demonstrating my ability to forget vital features of > >>> running my > >>> system, does anyone have an opinion about whether it is worthwhile > >>> running > >>> qpsmtpd under PPerl??? > >> > >> We're running it (mostly) at perl.org, because it really hides the > >> startup overhead, which can have a huge effect on the other things on > >> the machine when a lot of email is moving. > > > > I haven't been able to get PPerl to complete its tests properly - > > probably minor things, but I'm not going to implement it until such > > time > > as all tests work. > > I haven't seen reports from you :-) > > > I was wondering if it might be possible to compile qpsmtpd (along > > with the plugins) with perlcc. Is there anything preventing it, or > > might > > it require a lot of changes? > > perlcc isn't what you're looking for :-) It doesn't do what most people > expect (or work nearly as well as most people hope). > > Matt. > >
