Taking into consideration that in practice, people aren't going to put a CSS server on port 8000 or 43000. In general, most people cluster around 27015 and up. The way things are now, you only have up to 27019 before you run into the 27020 port from the first server on 27015. (And at that point, ports 27021 to 27024 are also in use) Its just a general note though, as I'd like to see a server that can reliably run more than that with all the servers full of players
I'm more worried about it ignoring the -ip command line and not being something that can be adjusted freely. People with businesses have used these ports already, for whatever reason, and given them to customers, and now they have to tell those customers that their port is changing with no real notice or warning. Customers aren't always understanding that the change is something outside of the provider's control.
----- Original Message ----- From: "Chris Jones" <[EMAIL PROTECTED]> To: <[email protected]> Sent: Wednesday, April 06, 2005 11:14 PM Subject: Re: [hlds_linux] Counter-Strike: Source and Source Engine update
Original message from Michael McKoy:
Makes it really tight to put a lot of servers on a machine.
You must run a LOT of servers, considering there are 2^16 (65536) ports available for binding, and only 1024 of them are reserved for system daemons. A little math shows that just over 20k servers could be run on a single box, if available ports were the only consideration.
-- Chris
_______________________________________________ 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
