***: fink has quit IRC (Quit: fink)
heavysixer has joined #arpnetworks
ChanServ sets mode: +o heavysixer
heavysixer has quit IRC (Quit: heavysixer)
heavysixer has joined #arpnetworks
ChanServ sets mode: +o heavysixer
heavysixer has quit IRC (Quit: heavysixer)
heavysixer has joined #arpnetworks
ChanServ sets mode: +o heavysixer
heavysixer has quit IRC (Quit: heavysixer)
fink has joined #arpnetworks
heavysixer has joined #arpnetworks
ChanServ sets mode: +o heavysixer
fink has quit IRC (Quit: fink)
heavysixer has quit IRC (Quit: heavysixer) hazardous: stupid question of the day: how do i check every second or two for processes that are using above a certain amount of cpu and kill -9 them as fast as possible ***: heavysixer has joined #arpnetworks
ChanServ sets mode: +o heavysixer brycec: Sounds potentially dangerous... But no doubt you could use top and awk to get the top couple of processess' PIDs and kill 'em. ***: heavysixer has quit IRC (Quit: heavysixer) mkb_: I hope your process killer doesn't use too much CPU ***: r0ni has joined #arpnetworks mnathani: mkb_: lol, it would simply end up killing itself if it did use too much CPU ***: staticsa1 has joined #arpnetworks
staticsafe has quit IRC (Disconnected by services)
staticsa1 is now known as staticsafe
Hien_ has joined #arpnetworks
joepie91_ has joined #arpnetworks
Hien has quit IRC (*.net *.split)
joepie91 has quit IRC (*.net *.split)
stevenc has quit IRC (*.net *.split)
stevenc has joined #arpnetworks
heavysixer has joined #arpnetworks
ChanServ sets mode: +o heavysixer
heavysixer has quit IRC (Quit: heavysixer)
heavysixer has joined #arpnetworks
ChanServ sets mode: +o heavysixer
heavysixer has quit IRC (Quit: heavysixer) hazardous: lol
brycec: it'll basically be something like ps aux | grep SPECIFIC_PROGRAM_STRING
shouldnt have any collateral damage mkb_: why do you want to do this? I fear that unless your process is limited by I/O or something, it will be using either no CPU or all of it brycec: I can see the utility if you're looking for runaway processes, something that's been running for a few minutes chweing up CPU... I myself monitor those and receive email alerts, but there is no automatic action. (eg when running a full backup, my alerts are set off, but it's harmless and I don't kill the backup)
If you're looking for that, there's a plugin distributed with munin-node that does just that -- IIRC, if the same process is running high for 2 or more consecutive runs (in other words, for at least 5 minutes), then it sends the alert mkb_: CPU time limits are an option too, but you have to be careful to exclude long-running stuff brycec: Start by excluding uid=0 ;p ***: mkb has joined #arpnetworks
mkb has quit IRC (Client Quit)
mkb has joined #arpnetworks
mkb_ has quit IRC (Quit: goodbye forever)
mkb has quit IRC (Client Quit)
mkb has joined #arpnetworks