#arpnetworks 2013-10-26,Sat

↑back Search ←Prev date Next date→ Show only urls(Click on time to select a line by its url)

WhoWhatWhen
***fink has joined #arpnetworks [04:17]
......................... (idle for 2h0mn)
fink has quit IRC (Quit: fink) [06:17]
.......... (idle for 48mn)
heavysixer has joined #arpnetworks
ChanServ sets mode: +o heavysixer
[07:05]
....... (idle for 31mn)
heavysixer has quit IRC (Quit: heavysixer) [07:36]
............... (idle for 1h13mn)
heavysixer has joined #arpnetworks
ChanServ sets mode: +o heavysixer
[08:49]
.................... (idle for 1h38mn)
heavysixer has quit IRC (Quit: heavysixer) [10:27]
......................... (idle for 2h2mn)
heavysixer has joined #arpnetworks
ChanServ sets mode: +o heavysixer
[12:29]
.......... (idle for 47mn)
heavysixer has quit IRC (Quit: heavysixer) [13:16]
fink has joined #arpnetworks [13:22]
..................... (idle for 1h41mn)
heavysixer has joined #arpnetworks
ChanServ sets mode: +o heavysixer
[15:03]
.......... (idle for 49mn)
fink has quit IRC (Quit: fink) [15:52]
heavysixer has quit IRC (Quit: heavysixer) [16:04]
hazardousstupid 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:14]
.... (idle for 18mn)
***heavysixer has joined #arpnetworks
ChanServ sets mode: +o heavysixer
[16:32]
brycecSounds potentially dangerous... But no doubt you could use top and awk to get the top couple of processess' PIDs and kill 'em. [16:36]
***heavysixer has quit IRC (Quit: heavysixer) [16:47]
....... (idle for 33mn)
mkb_I hope your process killer doesn't use too much CPU [17:20]
***r0ni has joined #arpnetworks [17:27]
..... (idle for 22mn)
mnathanimkb_: lol, it would simply end up killing itself if it did use too much CPU [17:49]
***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
[18:01]
......... (idle for 44mn)
heavysixer has joined #arpnetworks
ChanServ sets mode: +o heavysixer
[18:53]
heavysixer has quit IRC (Quit: heavysixer) [19:07]
heavysixer has joined #arpnetworks
ChanServ sets mode: +o heavysixer
[19:20]
heavysixer has quit IRC (Quit: heavysixer) [19:34]
......... (idle for 43mn)
hazardouslol
brycec: it'll basically be something like ps aux | grep SPECIFIC_PROGRAM_STRING
shouldnt have any collateral damage
[20:17]
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:27]
brycecI 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
[20:35]
mkb_CPU time limits are an option too, but you have to be careful to exclude long-running stuff [20:39]
brycecStart by excluding uid=0 ;p [20:40]
.............. (idle for 1h8mn)
***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
[21:48]

↑back Search ←Prev date Next date→ Show only urls(Click on time to select a line by its url)