>AMRECOVER Version 2.5.0. Contacting server on admin1.airscorp.com ...
>amrecover: did not get a reserved port: 50012
Yup, that appears to be broken.
You do understand, don't you, that 2.5 is the development version and
only folks prepared to do serious debugging on their should go down
path, right?
I'll take a look, but I suspect it'll get deep into the new security
framework, and I get really lost in there.
The old code would try for a reserved port first, which, since amrecover
runs as root, should have worked. Only if that failed would it fall
back to the port range or any unreserved port. I'm guessing it's now
going for the port range first.
The problem is, I'm not sure whether that's a good thing or a bad thing.
John R. Jackson, Technical Software Specialist, [EMAIL PROTECTED]
