The thing is I'm reading the output via pipe into my server monitor tool
to check if at the end it says "update successful". Now the amount of
text is so huge that I have to change my methods of handling/storing it
in the code (curse me for having used a fixed size array), and I'm not
very keen on working on that right now :))
On 2012/04/13 18:36, Saul Rennison wrote:
If it's automated why do you care about the amount of output? Surely you
aren't going to be looking at the output, and if you are, then something
probably went wrong. In which case, the output is helpful.
I can see absolutely 0 advantages, and several disadvantages, to
disabling verbose output.
Kind regards,
*Saul Rennison*
On 13 April 2012 17:29, Dominik Friedrichs <d...@forlix.org
<mailto:d...@forlix.org>> wrote:
I dont suppose there is an option such as -nonverbose to prevent the
huge amount of diagnostic lines from being displayed, for example
for automated applications?
On 2012/04/12 23:43, Fletcher Dunn wrote:
A new version of the HLDS Update Tool has been released. The
tool should automatically self-update the next time you run it.
(Linux users may need to re-run the tool after it self-updates
to complete the installation operation that was intended when
launching the tool.)
Changes:
* Added significant diagnostic output
* Fix bug causing the tool to restart the update process all
over from the beginning if there was an error with a single depot.
* Fix spurious "connection reset by peer" error when closing
connection to content server, which could cause the update to
restart from the beginning.
* Tool will now reuse a connection to a depot, rather than
disconnecting and reconnecting
* If the determines in the first pass that no files would
actually be updated from a particular depot, it will no longer
needlessly connect to that depot in the second pass
* Added -nobootstrapupdate option
Basically, we fixed a few of the most egregious things the tool
was doing that make a slow update much slower. Queuing to
connect to a content server still takes up the bulk of the
update time during peak times after a major update is released;
so don't expect miracles. However, we are hopeful that most
users will see modest speedup.
We also added quite verbose diagnostic output, so at least you
can tell what the tool is doing. Be aware that this output may
contain what appear to be "errors," especially when the tool is
trying to connect to a content server. Failures to connect are
normal and the tool has always experienced them and
automatically retried. The only thing new is that it is telling
you what it is doing.
Linux users: If you get the error message "Bad
uSizeOfSignature", then you probably have a bad version of the
tool, which was posted mistakenly for a few hours yesterday. To
get unstuck, replace the executable named "steam" with this one:
http://media.steampowered.com/__apps/440/linuxhldsupdatetool___48/steam
<http://media.steampowered.com/apps/440/linuxhldsupdatetool_48/steam>
Thanks to those of you who helped beta test this tool.
Thanks,
Fletcher
_________________________________________________
To unsubscribe, edit your list preferences, or view the list
archives, please visit:
https://list.valvesoftware.__com/cgi-bin/mailman/listinfo/__hlds
<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
<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
