nice catch!!!
didn't notice those log lines.

faking sched_setscheduler seems an interesting way to make it act
normale again :)

hope valve will step in and add an official and supported way to take
this out :)

Il 29/09/2012 23:38, Adam Nowacki ha scritto:
> I see this spammed hundreds of times every map change:
> 7588  22:52:42.714760 sched_setscheduler(7588, SCHED_RR, { 0 }) = -1
> EINVAL (Invalid argument)
> 7588  22:52:42.715275 sched_setscheduler(7588, SCHED_RR, { 2 }) = 0
>
> ... unexpected but has a nice side-effect for my servers - I have a
> script running from crontab (every minute) changing srcds priorities
> to RR 10. When changing map priority drops to 2 so impacts less other
> running servers.
>
> But this is undocumented and definitely needs some configurability -
> fix it Valve.
>
> For now you should be able to LD_PRELOAD a library with fake
> sched_setscheduler.
>
> On 2012-09-29 17:26, Marco Padovan wrote:
>> Hi,
>>
>> on centos5 and centos6 we are seeing srcds_linux that automatically
>> increase his own priority when creating the game threads
>>
>> I just start tf2 using srcds_run with the usual commands line, but it
>> automatically tries to push his own priority higher as soon as it
>> creates the threads...
>>
>> Is that and expected behaviour?
>>
>> How can I stop the process from changing his own priorities and just use
>> the one set for the parent script (srcds_run)?
>> _______________________________________________
>> 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

_______________________________________________
To unsubscribe, edit your list preferences, or view the list archives, please 
visit:
https://list.valvesoftware.com/cgi-bin/mailman/listinfo/hlds_linux

Reply via email to