innfeed 'discover' and wish list
rra at stanford.edu
Sat Jul 9 15:58:00 UTC 2005
Todd Olson <tco2 at cornell.edu> writes:
> Thanks for taking the time to look at this.
> So I am very puzzled.
> My experience is this:
> My box was a solaris 9 box with one physical and 3 logical interface.
> Initially innfeed was configured for a logical interface with an IP
> address that the remote peer server *rejected* the connection from.
> I am assuming (but have not verified) that when innfeed contacts a
> peer and that peer refuses the connection that the connection would
> be closed!
> When innfeed tries a few minuites later to contact the remote peer
> again a new connection would be opened.
> But based on my logs there was no change in the interface used.
I would expect so as well. I'm at a loss to explain that behavior given
the code. In INN 2.4, whenever a HUP signal is received, the
configuration file is re-read. If there is a bindaddress paramenter, a
global bind_addr variable is updated. Every time a new connection is
opened, that variable is used to specify the local bind address.
Russ Allbery (rra at stanford.edu) <http://www.eyrie.org/~eagle/>
Please send questions to the list rather than mailing me directly.
<http://www.eyrie.org/~eagle/faqs/questions.html> explains why.
More information about the inn-workers