cron and resched.sh

[dubzee]

Hi Guys,

Any idea's why after a couple of minutes when watching top my srcds process has a priority of -99 then drops to 0? unless I run resched.sh command manually..

I've added it to crontab -e.. ?

Thanks,
Alex.

[BehaartesEtwas]

do you run the resched.sh command as root from cron?

[dubzee]

Hi BehaartesEtwas,

First I tried adding */5 * * * * root /usr/local/sbin/resched.sh > /dev/null 2>&1 and restarted the daemon, then removed it and added to crontab -e only because using Ubuntu in the past I always used that.

Anyway since posting I do believe the cron job is working it just seems that sometimes the PR of srcds process drops to 0 from -99 until the cron job kicks back in?

Thanks for your help,
Alex.

[BehaartesEtwas]

I never observed this. Do you run the game servers as root (-> bad idea)? Or did you modify /etc/security/limits.conf? What I observed was some time ago, that the servers try to rise their priority by themselves. Normally this is not possible, but as root or with some settings in limits.conf they could do this. But if you set the priority yourself using resched.sh that might actually lower the priority...

I am pretty sure that under normal circumstances srcds does not lower its priority by itself. I don't use any cronjob to change priority but some tool that changes it only once at startup of the server. Still my servers have their priority after ~24h of running...

[dubzee]

Hi BehaartesEtwas,

No, each instance of srcds is ran as their own user not root, again no I haven't altered limits.conf :-(

It's strange because my other server running ubuntu works fine, this new server is running debian? very strange!

Thanks!

[BehaartesEtwas]

debian shouldn't make the difference... make sure you don't have any cronjob that changes priorities (like resched.sh) installed in any of the user accounts...

[dubzee]

Will have a look .. thanks for your help

Thanks,
Alex