Hi, thanks for your reply. In my case it is not srcds_run doing that, it's srcds_linux that does something.
"priority" changes a few seconds after srcds_linux has started (right after "create 4 threads" gets printed into the console log). In my case it's changing its own scheduling parameters moving from the SCHED_OTHER into SCHED_RR. Il 29/09/2012 18:16, Rudy Bleeker ha scritto: > On my ubuntu system srcds_linux has a priority of 20 (nice value 0), > which is the default for regular user processes. So no, I'm not seeing > the behaviour you describe. I also don't see anything in the srcds_run > script that looks like it's trying to increase process priority. > > On Sat, Sep 29, 2012 at 5:26 PM, Marco Padovan <e...@evcz.tk> 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
