[EMAIL PROTECTED] wrote:
As just installed, it appears that the run file invokes 'qpsmtpd'.
The qpsmtpd-server wants to use Qpsmtpd::SelectServer instead of
Qpsmtpd::TcpServer. Okay, what's the difference?
I don't think the SelectServer code is actually working; I believe that was
Matt's first attempt at writing a select() style server. If you want to
experiment, you can download the high_perf branch.
And since I want to run the forkserver version anyway, should my
run file use 'qpsmtpd-forkserver' instead of 'qpsmtpd'?
You don't need tcpserver with the forkserver installation. Personally, I use a
DJB envdir-style installation (which I keep meaning to commit to the repository
as an alternative mode of operation). My run file looks like this:
#!/bin/sh
exec 2>&1 \
envdir ./env \
sh -c '
exec \
softlimit ${DATALIMIT+"-d$DATALIMIT"} \
${PERL-perl} -T ./qpsmtpd-forkserver \
--listen-address "${IP-0}" \
--port "${PORT-25}" \
--limit-connections "${MAXCLIENTS-15}" \
--user "${QPUSER-smtpd}"
'
and I create env/* files as appropriate for the machine I am configuring. I had
to abstract out the ${PERL} executable because on two of the boxes I am not able
to run with the system perl.
HTH
John
