Trying to work with this has been such a headache. I'm running my servers at expense of my own time and bandwidth. I don't appreciate having such a half-baked administration tool forced into my workflow.
-Jeremy On Mar 25, 2013, at 8:56 PM, Jesse Molina <[email protected]> wrote: > > Basically, you can't run HLDSUpdateTool and SteamCMD in a multi-user > environment. You MUST install a tool/binary for each and every user in their > own ~/bin directory. > > Except that you can't even do that because SteamCMD poops it's ugly > 41-character temporary directories and custom libraries all over the place, > and you can't symlink to it. Symlinking to the HLDSUpdateTool works fine, > though I'm doubtful about it's self-updating process working correctly -- it > would probably overwrite the symlink. > > > > The take-away lesson is: never try to let these self-updating tools be used > by more than their owner user. > > I would go so far as to fix them so that they can't run if they have go+x > permissions, or are being executed by anyone other than their owner user. > That would prevent potential problems with the bootstrap process overwriting > files thus changing the owner and permissions. > > > > You have to cd into these tools installation directories each time you want > to use them. > > Unix people don't think this way. It's antithetical to the way everything on > unix works. > > > > Jeremy Agostino wrote: >> In a similar vein, I haven't been able to run it as another shell-only >> user due to the lack of home folder. I used to run the old update tool >> thru some scripts as a shell user. Steamcmd errors out when it can't >> save logs to the current user's home folder (since it doesn't exist). >> >> -Jeremy >> >> On Mar 25, 2013, at 5:36 AM, Jesse Molina <[email protected]> wrote: >> >>> >>> It is impossible to use steamcmd via a symbolic link. You must CD into >>> it's directory to use it. Because, potato. >>> >>> >>> >>> luser@host-->steamcmd.sh >>> /home/luser/bin/steamcmd.sh: line 29: /home/luser/bin/linux32/steamcmd: No >>> such file or directory >>> [~] >>> luser-->which steamcmd.sh >>> /home/luser/bin/steamcmd.sh >>> [~] >>> luser-->stat /home/luser/bin/steamcmd.sh >>> File: ‘/home/luser/bin/steamcmd.sh’ -> ‘steamcmd/steamcmd.sh’ >>> Size: 20 Blocks: 0 IO Block: 4096 symbolic link >>> Device: 903h/2307d Inode: 917517 Links: 1 >>> Access: (0777/lrwxrwxrwx) Uid: ( 1000/ luser) Gid: ( 1000/ luser) >>> Access: 2013-03-25 02:17:00.028625973 -0700 >>> Modify: 2013-03-25 02:17:00.028625973 -0700 >>> Change: 2013-03-25 02:17:00.028625973 -0700 >>> Birth: - >>> [~] >>> luser--> >>> >>> >>> >>> Also, while I am complaining... >>> >>> luser@host-->time ./steam >>> Checking bootstrapper version ... >>> Getting version 50 of Steam HLDS Update Tool >>> Downloading. . . . . . . . . . . . >>> Steam Linux Client updated, please retry the command >>> >>> real 12m43.141s >>> user 0m0.204s >>> sys 0m0.292s >>> [~/bin/hldsupdatetool] >>> >>> >>> >>> >>> -- >>> # Jesse Molina >>> # Mail = [email protected] >>> # Cell = 1-602-323-7608 >>> >>> >>> >>> _______________________________________________ >>> 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 > > -- > # Jesse Molina > # Mail = [email protected] > # Cell = 1-602-323-7608 > > > > _______________________________________________ > 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
