>I'm using the 2.4.2p2tapeio branch. This should behave like the normal
>2.4.2p2 version, right?
Yes.
I just looked at the code and it appears a change went in a while back
(like, 1999 :-), that flipped the order of port request attempts. It
used to be:
* try a reserved port.
* try the user specified port range if it has been defined.
* try anything.
The new order is:
* try the user specified port range if it has been defined.
* try a reserved port.
* try anything.
Just to confuse matters, amrecover used to do its own port management
rather than call the above code. It would only request a reserved port,
which is the right thing for it to do.
But that code segment contained another bug which I cleverly decided
could be handled by calling the common stream_client code, not realizing
the port problem. Oops. That's the change that went in recently that
triggered all this trouble.
There are several ways to deal with this, most pretty easy to implement,
but I want to ask over in amanda-hackers what people think is the best
way. When I get it worked out, I'll post a follow-up here with the patch.
Sorry 'bout that.
>Arjan
John R. Jackson, Technical Software Specialist, [EMAIL PROTECTED]
