[04:17] *** fink has joined #arpnetworks
[06:17] *** fink has quit IRC (Quit: fink)
[07:05] *** heavysixer has joined #arpnetworks
[07:05] *** ChanServ sets mode: +o heavysixer
[07:36] *** heavysixer has quit IRC (Quit: heavysixer)
[08:49] *** heavysixer has joined #arpnetworks
[08:49] *** ChanServ sets mode: +o heavysixer
[10:27] *** heavysixer has quit IRC (Quit: heavysixer)
[12:29] *** heavysixer has joined #arpnetworks
[12:29] *** ChanServ sets mode: +o heavysixer
[13:16] *** heavysixer has quit IRC (Quit: heavysixer)
[13:22] *** fink has joined #arpnetworks
[15:03] *** heavysixer has joined #arpnetworks
[15:03] *** ChanServ sets mode: +o heavysixer
[15:52] *** fink has quit IRC (Quit: fink)
[16:04] *** heavysixer has quit IRC (Quit: heavysixer)
[16:14] <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
[16:32] *** heavysixer has joined #arpnetworks
[16:32] *** ChanServ sets mode: +o heavysixer
[16:36] <brycec> Sounds potentially dangerous... But no doubt you could use top and awk to get the top couple of processess' PIDs and kill 'em.
[16:47] *** heavysixer has quit IRC (Quit: heavysixer)
[17:20] <mkb_> I hope your process killer doesn't use too much CPU
[17:27] *** r0ni has joined #arpnetworks
[17:49] <mnathani> mkb_: lol, it would simply end up killing itself if it did use too much CPU
[18:01] *** staticsa1 has joined #arpnetworks
[18:01] *** staticsafe has quit IRC (Disconnected by services)
[18:01] *** staticsa1 is now known as staticsafe
[18:04] *** Hien_ has joined #arpnetworks
[18:08] *** joepie91_ has joined #arpnetworks
[18:08] *** Hien has quit IRC (*.net *.split)
[18:08] *** joepie91 has quit IRC (*.net *.split)
[18:08] *** stevenc has quit IRC (*.net *.split)
[18:09] *** stevenc has joined #arpnetworks
[18:53] *** heavysixer has joined #arpnetworks
[18:53] *** ChanServ sets mode: +o heavysixer
[19:07] *** heavysixer has quit IRC (Quit: heavysixer)
[19:20] *** heavysixer has joined #arpnetworks
[19:20] *** ChanServ sets mode: +o heavysixer
[19:34] *** heavysixer has quit IRC (Quit: heavysixer)
[20:17] <hazardous> lol
[20:17] <hazardous> brycec: it'll basically be something like ps aux | grep SPECIFIC_PROGRAM_STRING
[20:18] <hazardous> shouldnt have any collateral damage
[20:27] <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
[20:35] <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)
[20:36] <brycec> 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
[20:39] <mkb_> CPU time limits are an option too, but you have to be careful to exclude long-running stuff
[20:40] <brycec> Start by excluding uid=0 ;p
[21:48] *** mkb has joined #arpnetworks
[21:48] *** mkb has quit IRC (Client Quit)
[21:50] *** mkb has joined #arpnetworks
[21:52] *** mkb_ has quit IRC (Quit: goodbye forever)
[21:54] *** mkb has quit IRC (Client Quit)
[21:55] *** mkb has joined #arpnetworks