Any news on a fix for this? Is a config flag also going to be added for choosing the port for whatever currently binds port 27005 (what is that BTW)? What about a flag to have server startup fail (instead of incrementing port) if the specified port is unavailable?
Thanks -Justin On Apr 6, 2005 4:37 PM, Alfred Reynolds <[EMAIL PROTECTED]> wrote: > Okay, I have found out why it is binding to 27030. This port is related > to the VAC2 Beta testing we are performing (and will continue to be used > once VAC2 becomes fully functional). For now the server will always try > to bind to 27030 on startup (so you can't run two servers on a single > machine with only 1 binding to port 27030). > We will add a configuration flag to enable you to move this VAC2 port to > a different number for cases when you want to bind to 27030 in a future > update. > > - Alfred > _______________________________________________ To unsubscribe, edit your list preferences, or view the list archives, please visit: http://list.valvesoftware.com/mailman/listinfo/hlds_linux
