My three test servers are still on the master list after 125 hours for the two servers behind a router and 100 hours for the server on it's own IP.
Removing the high-res timer appears to have solved this problem. None of the servers stayed on the master list more then 40 hours before this. ----- Original Message ----- From: "Kevin Ottalini" Sent: Monday, June 13, 2005 7:12 PM Subject: Servers Stay on Master List
I've been doing a lot of testing with HL2DM and CS:S servers to try and identify when/why they fall off the master list. My test scenario is two servers behind a linksys BEFSR41 router which owns a static IP address and one server direct on it's own static IP address. All systems are XP Pro Win32, the systems run nothing but HL2 Servers. All test servers share the same dsl line that also hosts a 24/7 HLDM server. All servers suffer the same line outages (my dsl resets itself from time to time). I found that within 30 to 40 hours all HL2 servers (behind a router or not) would stop communicating with the master list server. (This would indicate that the problem has nothing to do with the server being behind a router.) One thing I've recently stumbled on is that if I do NOT run a high-res timer on the systems, all the servers will remain on the master list. Currently 78 hours on for the two servers behind a router and 50 hours for the server on it's own IP. Can anyone correlate this for me on their servers? I'm unsure what the Linux equivalent would be for this, but I'll copy the linux list as well. qUiCkSiLvEr
_______________________________________________ To unsubscribe, edit your list preferences, or view the list archives, please visit: http://list.valvesoftware.com/mailman/listinfo/hlds_linux
