I've got a related question about HLTV: I thought that HLTV was a seperate app that bound to the HL server on the standard listen port (27015) and opened a listen port for spectators to connect to. So then why are CS and CSS ded servers opening port 27020 for?
Also, just curious: are there cmd line params for hlds_run for disabling the hltv port similar to srcds_run -nohltv? When HLTV is non-beta in source, will there be a way to set the HLTV port? Sorry if any of these are dumb questions... -Justin On Sun, 20 Feb 2005 03:45:00 +0100, Thiesson Johann <[EMAIL PROTECTED]> wrote: > -- > Hi, > > Can we hope having the HLTV port binding problem solved ? > Or any way to disable it until it's fixed ? > > Having several HL:S servers on a single machine is a nightmare. > Especially if you have servers running on 27020. > > I would appreciate to see the "auto binding" thing disabled too. > On the current version, if the server try to bind the port X, and the > port X is already used, the process will use X+1. > If the port is not available, the server should NOT start I think. > I can't see the advantage of this. If the port is already used, there > is a problem! We expect the server running fine on port X, or not > running at all. Players are waiting for their server on port X, not on > port X+1. > > Imagine if the ftpd servers were like that. You lanch 2 ftp > servers. Port 21 is used. So the second goes automatically on port 22 ? > What the point o_O > > -- > Thiesson Johann > -- > Content-Description: Digital signature > > [ signature.asc of type application/pgp-signature deleted ] > -- > > _______________________________________________ > To unsubscribe, edit your list preferences, or view the list archives, please > visit: > http://list.valvesoftware.com/mailman/listinfo/hlds_linux > _______________________________________________ To unsubscribe, edit your list preferences, or view the list archives, please visit: http://list.valvesoftware.com/mailman/listinfo/hlds_linux
