Charlie Brady wrote:
You should reply on-list.
---------- Forwarded message ----------
Date: Wed, 27 May 2009 12:45:37 -0500
From: David Favor <da...@davidfavor.com>
To: Charlie Brady <charlieb-qpsm...@budge.apana.org.au>
Subject: Re: Feature request to disable CONTROL_PORT
I mistyped. Try:
egrep -i "config_port|config_server"
I've already been talking with Matt. He said he'd already
been considering stripping this out, as there's no real
added benefit, only added complexity for multi-instance
sites.
Charlie Brady wrote:
On Wed, 27 May 2009, David Favor wrote:
> Having qpsmtpd listen on an additional control port
> creates serious complexity when running multiple
> copies of qpsmtpd, as each copy has to somehow figure
> out which control port to use, hope it's free and then
> connect.
Please clarify what you mean:
$ cd qpsmtpd/
$ grep -r CONTROL_PORT .
$ grep -r -i CONTROL_PORT .
$
> I usually just strip this code out of qpsmtpd or
> comment out the initial connection.
What code do you strip out?
> A great feature to add is a simple command line option
> to turn this off.
It sounds as though you might be running qpsmtpd with multiple
--listen-address options. If so, why are you trying to run multiple
copies
of qpsmtpd?
--
Love feeling your best ever, all day, every day?
Click http://RadicalHealth.com for the easy way!
