What this guy said. If you are sending clients a kiss-of-death packet,
please at least acknowledge it on the client.
David A. Parker wrote:
If Command aborted means the servers are full, then perhaps they
should reword that message.
Thanks.
- Dave
On 10/13/2011 05:15 PM, Andrew DeMerse
Do you perhaps have verify all in your update command line? I removed that and
it worked. Dunno if that could really be it though.
Sent from my iPhone 4
On Oct 13, 2011, at 11:21 PM, Jesse Molina je...@opendreams.net wrote:
What this guy said. If you are sending clients a kiss-of-death
I was using -verify_all in the update command line when I received this
error. I left the server down over night and then tried the update
again this morning, and it worked.
Command aborted just sounds so dire. A message like that makes me
think something went seriously wrong. It seems to
From my understanding, the tool should keep retrying when it gets that error
using the -retry command prompt, however it is not.
On Fri, Oct 14, 2011 at 7:54 AM, David A. Parker dpar...@utica.edu wrote:
I was using -verify_all in the update command line when I received this
error. I left the
Is anyone seeing this when they attempt to update TF2?
Checking bootstrapper version ...
Updating Installation
Command aborted
CAsyncIOManager: 0 threads terminating. 0 reads, 0 writes, 0 deferrals.
CAsyncIOManager: 15 single object sleeps, 0 multi object sleeps
CAsyncIOManager: 0 single object
The servers are being hammered, just give it some time.
On Thu, Oct 13, 2011 at 5:14 PM, David A. Parker dpar...@utica.edu wrote:
Is anyone seeing this when they attempt to update TF2?
Checking bootstrapper version ...
Updating Installation
Command aborted
CAsyncIOManager: 0 threads
If Command aborted means the servers are full, then perhaps they
should reword that message.
Thanks.
- Dave
On 10/13/2011 05:15 PM, Andrew DeMerse wrote:
The servers are being hammered, just give it some time.
On Thu, Oct 13, 2011 at 5:14 PM, David A. Parkerdpar...@utica.edu wrote:
yes, getting a lot of them..
client instead is updated... sadly there are no servers to play on...
why don't they give priority to servers...? :D
Il 13/10/2011 23:14, David A. Parker ha scritto:
Is anyone seeing this when they attempt to update TF2?
Checking bootstrapper version ...
The best way to avoid this one is to use the -retry switch.
The old version just used to just sit there forever. Sometimes it still
does this, but I'd rather have it abort rather than just sit there forever.
On Thu, Oct 13, 2011 at 5:20 PM, David A. Parker dpar...@utica.edu wrote:
If Command
9 matches
Mail list logo
