Hi

Sorry for digging up this old email. It's been awhile since I've had time to work on my server control scripts and I'm grepping old mail.

I want to second what was said below. Any sane program would exit with an error status if it's manually allocated resources were already in use, but the source server doesn't do that.

I consider this a bug and implore the developers to fix it. Even if you had to add a new command line flag to permit for backwards compatible behavior, that would be okay. Something like -explicitports or whatever.

While I'm complaining...

It would also be nice if ports actually used what port they are told to use! For example, if you assign set "-steamport 26013", the process will actually bind to port 26014 instead, making it necessary to allocate resources in an odd order to prevent trampling (11, 13, 15, etc).



Claudio Beretta wrote:
Another thing rather unusual in a server is that srcds binds to the next
available port if the the main one is already taken. Most servers  in this
case would print an angry error message and then quit. What happens with
srcds is that the server start apparently fine, and you end up scratching
your head trying to figure out why it doesn't reply until you open netstat.

--
# Jesse Molina
# Mail = [email protected]
# Page = [email protected]
# Cell = 1.602.323.7608
# Web  = http://www.opendreams.net/jesse/



_______________________________________________
To unsubscribe, edit your list preferences, or view the list archives, please 
visit:
http://list.valvesoftware.com/mailman/listinfo/hlds_linux

Reply via email to