This was the point where the server got the defunct state in the past. This is possible the fix.
> As a quick update, the is definitely happening when a game ends and > people leave the server. The fork completely stops responding for about > 30 seconds. Is this one of those matchmaking "improvements" perhaps? > > David A. Parker wrote: >> Hello, >> >> I ahve noticed this three times in the last few hours. One of my L4D >> forks will stop responding to A2S_INFO queries and appear to be down. >> When I log in to the server and telnet to the netcon port of the "dead" >> fork, type "status", wait anywhere from 10 seconds to one minute, and >> then suddenly I will get the status output and the fork will be back, >> running as it should. I haven't been watching too closely, but this >> seems to happen when a game finishes and people leave the server. >> >> Has anyone else seen this? >> >> - Dave >> > > -- > > Dave Parker > Utica College > Integrated Information Technology Services > (315) 792-3229 > Registered Linux User #408177 > > _______________________________________________ > 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
