That's more helpful, but still not the optimum behaviour. By allowing the
server to starts on port Y you could well be disrupting another server
or service on the machine perpetuating the problem.
The correct behaviour, if a port has been explicitly requested, should be
to log the error and quit, that way the admin will know exactly what the
problem is and it wont affect other servers or services.
Regards
Steve
----- Original Message -----
From: "Jon Lippincott" <[email protected]>
I just fixed this. If the desired port isn't available you'll get a message
like this:
WARNING: Port X was unavailable - bound to port Y instead.
This will go out in the next update.
================================================
This e.mail is private and confidential between Multiplay (UK) Ltd. and the person or entity to whom it is addressed. In the event of misdirection, the recipient is prohibited from using, copying, printing or otherwise disseminating it or any information contained in it.
In the event of misdirection, illegible or incomplete transmission please
telephone +44 845 868 1337
or return the E.mail to [email protected].
_______________________________________________
To unsubscribe, edit your list preferences, or view the list archives, please
visit:
http://list.valvesoftware.com/mailman/listinfo/hlds_linux
