On Fri, Jul 27, 2007 at 12:18:14PM -0400, Chaskiel M Grundman wrote:
> I asked the developers why the code was there, because on systems where
> "servername" points at an alias instead of a single name, the bind tends to
> fail and spams the syslog. These extra error messages confused debugging
> efforts on more than one occasion. It appears that nobody knew, and so the
> code was pulled out. if the bind is restored, I would prefer that it use a
> dedicated config parameter, and not re-use servername
A separate config parameter that defaults to the servername if the
latter is set is fine.
> I would only expect this to happen if you have asymmetric routing. (i.e. B
> refuses to route along the inverse of the path that A routes to B)
No routing, just basic firewalling: the replica only accepts connections
from the master's IP address. But the machine hosting the master also
runs other services on other IP addresses.
Gabor
--
---------------------------------------------------------
MTA SZTAKI Computer and Automation Research Institute
Hungarian Academy of Sciences
---------------------------------------------------------
----
Cyrus Home Page: http://cyrusimap.web.cmu.edu/
Cyrus Wiki/FAQ: http://cyrusimap.web.cmu.edu/twiki
List Archives/Info: http://asg.web.cmu.edu/cyrus/mailing-list.html
