> ----- Original Message -----
> From: "Sean Chittenden" <[EMAIL PROTECTED]>
> To: "Per Einar" <[EMAIL PROTECTED]>
> Cc: <[EMAIL PROTECTED]>
> Sent: Sunday, April 08, 2001 11:42 AM
> Subject: Re: Sendmail or not?
>
>> if you | to sendmail, then you still fork. Mail::Sendmail, I
>> bet dime to dollar, forks and execs a process. The only way to avoid
>> forking is to open a socket and send the message via SMTP (or QMQP if
>> you want to pimp your system out with qmail). Unless you're on AIX or
>> solaris and performance is an issue, fork and get the job done w/
>> minimal headaches. -sc
>
> No, Mail::Sendmail sends through SMTP. That's why I talked about it.
> So, you're saying that I should just fork anyway? Will there be a big
> performance loss on Linux? And should I use Apache::Subprocess for
> this, or
> just go ahead with a standard pipe?
Oh man, have I been here.
After starting with forking, and then graduating to Mail::Sendmail,
we finally realized that you could have your cake (queuing) and eat
it too (no forking) by using Mail::Sendmail to deliver messages for
relay to a mailhost (even if it's the same machine).
Performance is best the mailhost is a dedicated machine, or load
balanced group of systems.
On Sunday, April 8, 2001, at 02:52 AM, Per Einar wrote:
--
-- Tom Mornini
-- ICQ 113526784
