I could think of one scenario: You start the server as one user, but that user doesn't have access to the nice command, but you run the renice crontab as root every 5 mins to ensure the proper values. That's not how I do it, but it's a guess.
-----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Ondrej Hošek Sent: Tuesday, July 31, 2007 4:30 PM To: [email protected] Subject: Re: [hlds_linux] Priority question Why renice when you can nice it directly while it starts? Or does that break things too? ~~ Ondra On 31.07.07 22:16 Uhr, ics wrote: > It wasnt always like that. I could just manually renice the process > before but after some updates, it became like that. Valve's only advice > was not to renice to process. Duh. > > -ics > > Dan E kirjoitti: >> -- >> [ Picked text/plain from multipart/alternative ] >> Well, so far with the method that I described earlier, I'm not eating >> 100% (maybe 40% average with 10 bots) :) So I think this method is >> safe to use :-D >> >> Dan >> >> karumba <[EMAIL PROTECTED]> wrote: ics schrieb: >> >>> [...]Try renicing the process yourself >>> and see what it does. The result you should see would be srcds eating >>> 100% of the CPU. >>> >> >> same here. i never understood that behaviour of the source dedi-server, >> that eats 100% CPU when reniced. _______________________________________________ To unsubscribe, edit your list preferences, or view the list archives, please visit: http://list.valvesoftware.com/mailman/listinfo/hlds_linux _______________________________________________ To unsubscribe, edit your list preferences, or view the list archives, please visit: http://list.valvesoftware.com/mailman/listinfo/hlds_linux
