I've seen most of this thread already and not disagreeing with anything
already said, but there is also a decent sourcemod plugin called "server
crontab" I've been using for years now.  It is quite stable and not too
picky about the game/mod (although IIRC it doesn't work on L4D/L4D2
because of hibernating).

Here's the SM forums post for it:
https://forums.alliedmods.net/showthread.php?p=523298

I use it to reboot the servers each day at 6am, and also have it do an
sm_hsay a few times (starting at 10 'til 6am) to pop up a hintbox msg that
the server will be doing its daily reboot in a few minutes.

Although from the sounds of it, not sure once a day would be enough. 
Could always set it up to reboot more frequently I guess.

FWIW these are the jobs I run:

// SERVER REBOOT WARNINGS
sc_addjob ? ? 5 5 50 51 "sm_hsay Daily Game Reboot in 10 Minutes"
sc_addjob ? ? 5 5 55 56 "sm_hsay Daily Game Reboot in 5 Minutes"
sc_addjob ? ? 5 5 57 58 "sm_hsay Daily Game Reboot in 3 Minutes!"
sc_addjob ? ? 5 5 59 0 "sm_hsay Daily Game Reboot in 1 Minute!!!"

// Reboot the server everyday of the week at 6am
sc_addjob ? ? 6 6 0 1 "quit"

Has worked very reliably for me.  The one "note" is - just something to be
aware of - it doesn't fire at exactly the top of the minute, it can happen
at any time during that minute (thus my "start time" of 5:50am and "stop
time" of 5:51am for the reboot in 10 minutes hsay, for example).



> I always thought this was par for the course for srcds.  This same thing
> happens to my TF2 servers running on Debian Squeeze.
>
> On 9/9/2012 11:28 AM, Mike Didiano wrote:
>>
>> Been having issues with*memory*problems for CS:GO on Windows server
>> 2008. Every map change the*memory*seems to go up around 50MB(possibly
>> caching all map files?) but they are not released at the next map
>> change.
>>
>> After half a day of running a full server*memory*usage is up over
>> 700mb and usually tops out just over 900mb. The higher the memory
>> usage, the worse the server performance gets.  Tops out just over
>> 900mb and at this point the game is unplayable.
>>
>>
>> Is valve aware of this or are there any fixes other than restarting
>> the server every 4 hours?
>>
>>
>>
>> _______________________________________________
>> 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


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

Reply via email to