cvsuser 04/03/10 20:08:00
Modified:.Tag: branch_0_27 Changes
Log:
add date stamp to Changes file
Revision ChangesPath
No revision
No revision
1.62.2.1 +1 -1 qpsmtpd/Changes
Index: Changes
cvsuser 04/03/10 20:12:15
Modified:.Changes LICENSE
Log:
2004 license
update Changes
Revision ChangesPath
1.64 +5 -1 qpsmtpd/Changes
Index: Changes
===
RCS file:
On 9 Mar 2004, at 22:32, ross mueller wrote:
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:
On Wed, 10 Mar 2004, Matt Sergeant wrote:
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
I'm curious as to whether anyone has built a forking server around qpsmtpd
(essentially doing what tcpserver does, but in perl)? I'm aware of the
select server version(*), but would prefer a forking server (say, using
Net::Daemon). That would seem to be able to provide the same speedup as
On Wed, 10 Mar 2004, Robert Spier wrote:
I'm curious as to whether anyone has built a forking server around qpsmtpd
(essentially doing what tcpserver does, but in perl)? I'm aware of the
select server version(*), but would prefer a forking server (say, using
Net::Daemon). That would seem
pperl is pre-forking.
Yes, but SelectServer isn't.
SelectServer doesn't fork at all.
It doesn't fork on every connection. The forking on every connection is
part of what causes some of the overhead.
Do you have evidence that that is the case? Fork should be inexpensive,
and it's
On Wed, 10 Mar 2004, Robert Spier wrote:
It doesn't fork on every connection. The forking on every connection is
part of what causes some of the overhead.
Do you have evidence that that is the case? Fork should be inexpensive,
and it's certainly not a problem with tcpserver.
thk Ask, finally 0.27 out :)
btw i having problem with spamassasin, why if i activate spamassasin
plugins, user who recive/open email with microsoft outlook have corrupt
header and attachment. this is not happen if i dont load spamassasin
plugins and with other mail client such evolution.
when i
