The srcds_run script probably is calling the wrong command to update. Thanks, I'll fix that.
I think in general that you *should* be able to use steamcmd.sh to launch the tool, without seting any environment variables, etc. (If you find any instructions telling you to do that, I think they are a bit old.) -----Original Message----- From: [email protected] [mailto:[email protected]] On Behalf Of Doctor McKay Sent: Thursday, February 21, 2013 2:29 PM To: Half-Life dedicated Linux server mailing list Subject: Re: [hlds_linux] [BUG] SteamCMD on Linux autoupdate blocker '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://me > dia.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
