https://en.wikipedia.org/wiki/Rubber_duck_debugging

On Thu, Feb 21, 2013 at 11:14 PM, Alfred Reynolds
<[email protected]> wrote:
> "rubber duck the problem" ? That is a new one on me
>
>
>
> -----Original Message-----
> From: [email protected] 
> [mailto:[email protected]] On Behalf Of Eric G. Wolfe
> Sent: Thursday, February 21, 2013 3:12 PM
> To: [email protected]
> Subject: Re: [hlds_linux] [BUG] SteamCMD on Linux autoupdate blocker
>
> Yeah, I get that 'steam' is an old part of the HldsUpdateTool.  I was
> trying to rubber duck the problem and point out this should probably
> call steamcmd.sh, instead of the legacy steam binary.
>
> Also, thanks Doctor for your awesome auto_steam_update plugin :)
>
> On 02/21/2013 05:29 PM, Doctor McKay wrote:
>> 'steam' is the name of the old HldsUpdateTool binary. I'm going to assume
>> that SteamCMD autoupdate functionality hasn't been implemented yet.
>>
>>
>> Doctor McKay
>> http://www.doctormckay.com
>> [email protected]
>>
>>
>> On Thu, Feb 21, 2013 at 5:11 PM, Eric G. Wolfe 
>> <[email protected]>wrote:
>>
>>> In trying out SteamCMD with the Team Fortress 2 Beta, a clean install
>>> seems to be missing something which would allow auto-update to function
>>> correctly.  Perhaps I am missing something obvious, or doing something
>>> wrong.  So I'll document my setup to reproduce.
>>>
>>> I restarted the TF2 Beta server after the update was shipped last night
>>> via `_restart` on the console.  It shuts down the server, but just comes
>>> back up saying "Master Server Requesting Restart", and never actually
>>> updating the server.  Isn't the dedicated server supposed to auto-update
>>> via steamcmd, or is auto-update not implemented?  I blew away the whole
>>> install and re-installed from scratch to see if I could reproduce the
>>> problem.
>>>
>>> # adduser steamcmd
>>> $ su - steamcmd
>>> $ mkdir ~/bin
>>> $ wget 
>>> http://media.steampowered.com/**client/steamcmd_linux.tar.gz<http://media.steampowered.com/client/steamcmd_linux.tar.gz>
>>> $ cd ~/bin && tar zxvf ../steamcmd_linux.tar.gz
>>> $ bash -l
>>> $ steamcmd.sh +login anonymous +app_update 229830 validate +quit
>>> $ $GAME_DIR/srcds_run -autoupdate ...
>>>
>>> So here might be relevant output from when the TF2 Beta server is started
>>>
>>> Auto detecting CPU
>>> Using default binary: ./srcds_linux
>>> Server will auto-restart if there is a crash.
>>> WARNING: Failed to locate steam binary.
>>> WARNING: Could not locate steam binary:, ignoring.
>>>
>>> Which is from Line #300 of srcds_run, and clearly shows `which steam`.
>>>   Now, I don't know if this should be looking for `steamcmd.sh`, `steam.sh`,
>>> or the old `steam` binary which hldsupdatetool downloads.  Running `find
>>> -type f -iname "steam"` returns nothing in this cleanly installed steamcmd
>>> managed home directory.
>>>
>>> If a `steam` binary is needed, which I expect provides auto-update
>>> functionality.  Why hasn't steamcmd downloaded that `steam` binary and put
>>> it into this managed directory?  If that is not the case, where did I go
>>> wrong?
>>>
>>> --
>>> Eric G. Wolfe
>>> Senior Linux Administrator,
>>> IT Infrastructure Systems
>>> ------------------------------**--------
>>> Marshall University Computing Services
>>> Drinko Library 428-K
>>> One John Marshall Dr.
>>> Huntington, WV 25755
>>> Phone: 304.942.3970
>>> Email: [email protected]
>>>
>>> You will be recognized and honored as a community leader.
>>>
>>>
>>> ______________________________**_________________
>>> To unsubscribe, edit your list preferences, or view the list archives,
>>> please visit:
>>> https://list.valvesoftware.**com/cgi-bin/mailman/listinfo/**hlds_linux<https://list.valvesoftware.com/cgi-bin/mailman/listinfo/hlds_linux>
>>>
>> _______________________________________________
>> To unsubscribe, edit your list preferences, or view the list archives, 
>> please visit:
>> https://list.valvesoftware.com/cgi-bin/mailman/listinfo/hlds_linux
>
>
> _______________________________________________
> To unsubscribe, edit your list preferences, or view the list archives, please 
> visit:
> https://list.valvesoftware.com/cgi-bin/mailman/listinfo/hlds_linux
>
> _______________________________________________
> To unsubscribe, edit your list preferences, or view the list archives, please 
> visit:
> https://list.valvesoftware.com/cgi-bin/mailman/listinfo/hlds_linux

_______________________________________________
To unsubscribe, edit your list preferences, or view the list archives, please 
visit:
https://list.valvesoftware.com/cgi-bin/mailman/listinfo/hlds_linux

Reply via email to