bind(0) will give you an arbitrary port - which is what you want, but there's a slim danger of acquiring a port that another daemon (not currently running) explicitly requires. By allowing the specification of a range at least means you have some control to facilitate avoidance.
Stuffed daemon goes perfectly with a fine Port (ho ho!) Cheers Mark On 6/7/07, Alan Conway <[EMAIL PROTECTED]> wrote:
On Tue, 2007-06-05 at 21:16 +0100, Mark Atwell wrote: > I would suggest favouring a range of ports - possibly trying one at a time, > bind(0) has the chance of stuffing other perfectly honourable daemons (if > that isn't an oxymoron! :o) Of course, in turn the range could be > configurable from 0 thru 64K if necessary. > I've worked lots with bind(0) servers and didn't have any stuffed daemons (sounds delicious though.) What were the circumstances of aforementioned daemon stuffing? All I'm looking for is a simple way to run several copies of a test suite simultaneously on the same host without confusion daemons. Cheers, Alan.
