I do that on the master servers that are later used to redistribute the
updates to all the slaves when needed/requested

I'm not running steamcmd against a running server :)

Il 22/08/2012 18:54, Russell Smith ha scritto:
> Why would you run this in a crontab?  Wouldn't you be potentially
> updating the server files while the server is running?
>
> On 22.08.2012 09:49, Andrew Caron wrote:
>> I have it running in a crontab and it is doing fine.
>>
>> Quite possible your permissions are wrong:
>> ln: creating symbolic link `//.steampath: Permission denied
>> /home/username/steamdirectory/steam.sh: line 24: //.steampid:
>> Permission
>>  denied 
>>
>> Or you can not use relative pathing. I am using absolute and there are
>> no problems.
>>
>> On Wed, Aug 22, 2012 at 8:24 AM, Marco Padovan <[email protected] [3]>
>> wrote:
>>
>>> As currently csgo do not support autoupdate I have to frequently run
>>> steamcmd from crontab.
>>>
>>> The only problem is that when trying to run it within this script:
>>>
>>> cd /home/username/steamdirectory/
>>> STEAMEXE=steamcmd /home/username/steam.sh +login steamuser
>>> steampassword
>>> +runscript update-slave.txt
>>>
>>> update-slave.txt content is:
>>> force_install_dir ../
>>> app_update 740
>>> exit
>>>
>>> I get the following output on centos6.3 x64:
>>>
>>> ln: creating symbolic link `//.steampath: Permission denied
>>> /home/username/steamdirectory/steam.sh: line 24: //.steampid:
>>> Permission
>>> denied
>>> Installing breakpad exception handler for
>>> appid(steam)/version(1345509297)
>>> unlinked 0 orphaned pipes
>>> CAsyncIOManager: 0 threads terminating.  0 reads, 0 writes, 0
>>> deferrals.
>>> CAsyncIOManager: 35 single object sleeps, 1 multi object sleeps
>>> CAsyncIOManager: 0 single object alertable sleeps, 1 multi object
>>> alertable sleeps
>>> [  0%] Checking for available updates...
>>> [  0%] Download complete.
>>> [----] Verifying installation...
>>> [----] !!! Fatal Error: Steam failed to load:
>>> *SteamStartEngine(0xff9a4900) failed with error 1: Failed to create
>>> directory /steam
>>>
>>> In order to get it working properly I had to set the $HOME variable
>>> before calling steam.sh
>>>
>>> HOME="/home/username"
>>>
>>> as steam.sh makes use of ~/ path multiple times...
>>>
>>> _______________________________________________
>>> Csgo_servers mailing list
>>> [email protected] [1]
>>> https://list.valvesoftware.com/cgi-bin/mailman/listinfo/csgo_servers
>>> [2]
>>
>>
>>
>> Links:
>> ------
>> [1] mailto:[email protected]
>> [2] https://list.valvesoftware.com/cgi-bin/mailman/listinfo/csgo_servers
>> [3] mailto:[email protected]
>
>
> _______________________________________________
> Csgo_servers mailing list
> [email protected]
> https://list.valvesoftware.com/cgi-bin/mailman/listinfo/csgo_servers

_______________________________________________
Csgo_servers mailing list
[email protected]
https://list.valvesoftware.com/cgi-bin/mailman/listinfo/csgo_servers

Reply via email to