Wow! My server actually restarted itself at round end when the master server sent an update notice. I didn't have to stop it myself to start updating. That's a first. Thanks for the smooth update, Valve. It was flawless if I do say so myself.
On Thu, Mar 1, 2012 at 8:53 PM, John Marbury <[email protected]> wrote: > Hat-serving system. > > > > > On Thu, Mar 1, 2012 at 8:51 PM, E. Olsen <[email protected]> wrote: > >> Agreed....although, wasn't there supposed to be some kind of >> content-serving system upgrade that was supposed to solve these kinds of >> bottlenecks? >> >> On Thu, Mar 1, 2012 at 8:47 PM, DarthNinja <[email protected]>wrote: >> >>> Why is it every update people go "Command aborted??? is something >>> wrong???" like its something new? >>> The content servers are busy updating all the clients and aren't >>> allowing servers to get the updates. Ether auto-update your servers the >>> second an update is released, or do it after the rush ends. >>> >>> inb4 "why doesn't valve give servers priority?". >>> >>> _______________________________________________ >>> To unsubscribe, edit your list preferences, or view the list archives, >>> please visit: >>> https://list.valvesoftware.com/cgi-bin/mailman/listinfo/hlds >>> >>> >> >> _______________________________________________ >> To unsubscribe, edit your list preferences, or view the list archives, >> please visit: >> https://list.valvesoftware.com/cgi-bin/mailman/listinfo/hlds >> >> > > _______________________________________________ > To unsubscribe, edit your list preferences, or view the list archives, > please visit: > https://list.valvesoftware.com/cgi-bin/mailman/listinfo/hlds > >
_______________________________________________ To unsubscribe, edit your list preferences, or view the list archives, please visit: https://list.valvesoftware.com/cgi-bin/mailman/listinfo/hlds
