New facilitator prompting for port

• Messages sorted by: [ date ][ thread ][ subject ][ author ]
• Next message: John Dowding: "OAA library for Perl"
• Previous message: Adam Cheyer: "Re: writeBB <-> readBB question"

When I start a new facilitator on a host/port that already has one
running, it used to just die silently (which was fine). Now it
prompts:

Exception reported:
tcp_mishap(tcp_listen.bind,48)

Currently unable to access gansett port 5082.
Try again? [y)es, n)o, c)hange, h)elp]:

and I have to respond 'no' all the time.

Can I get the old behavior back?

• Next message: John Dowding: "OAA library for Perl"
• Previous message: Adam Cheyer: "Re: writeBB <-> readBB question"