Hi,
I am wondering if one could _enforce_ a port when starting a CS:Source dedicated server on Linux. I have noticed that defining +port xxxxx does not necessarily mean that the server will be listening that port. The software seems to try it at first, but if it fails to bind to the port given, it will try next ports until it succeeds.
However, I have got a situation where it is better not to start the server at all - - in any port - - if the given port cannot be used.
Is there a way to prevent srcds from auto-defining the port?
The original Half-Life's hlds works as I described.
I am wondering if one could _enforce_ a port when starting a CS:Source dedicated server on Linux. I have noticed that defining +port xxxxx does not necessarily mean that the server will be listening that port. The software seems to try it at first, but if it fails to bind to the port given, it will try next ports until it succeeds.
However, I have got a situation where it is better not to start the server at all - - in any port - - if the given port cannot be used.
Is there a way to prevent srcds from auto-defining the port?
The original Half-Life's hlds works as I described.