-- On Thu, 8 Dec 2005 13:47:02 +0100 <[EMAIL PROTECTED]> bubbled: > The "problem" is as follows ... uhm ... first i'll try to explain the > foretime behaviour: > > We already had three processes in one server: > > First proc.: we launched a screen to attach and detach the console > Second proc.: srcds_run was fired up by screen > Third proc.: the main process: srcds_amd was fired up by the srcds_run > script due to the detection auf the processor architecture. > > Quite simple to boost the main process using "renice" to get a higher > process priority. > > From now on something has changed to get five processes: > > First proc.: we launched a screen to attach and detach the console > Second proc.: srcds_run was fired up by screen > Third proc.: one of three main processes: srcds_amd was fired up by > the srcds_run script due to the detection auf the processor > architecture. Fourth proc.: fired up by third proc. ... don't know > why and what ... it's a real process, not only a "thread" > Fifth proc.: fired up by fourth proc. ... don't know why and what ... > it's a real process, not only a "thread" > > I don't know which process to "renice" ... that's the problem.
What about nice?! Like set prio of -10: nice -n -10 ./srcds_run ... That whould give also the childs the prio. Another way: ps + grep + sed, or awk... So there is no real problem if you know the power of linux/unix! Martin -- MyExcuse: Temporal anomaly Martin Zwickel <[EMAIL PROTECTED]> Research & Development TechnoTrend AG <http://www.technotrend.de> -- [ signature.asc of type application/pgp-signature deleted ] -- _______________________________________________ To unsubscribe, edit your list preferences, or view the list archives, please visit: http://list.valvesoftware.com/mailman/listinfo/hlds_linux
