On 30/03/2008 5:08 PM, Justin Mason wrote:
> Daryl C. W. O'Shea writes:
>> Seems to be doing a whole lot of something, all the time...
>>
>> load averages:  1.00,  1.05,  1.13
>> 05:30:27
>> 57 processes:  55 sleeping, 2 on cpu
>> CPU states: 49.7% idle, 50.0% user,  0.3% kernel,  0.0% iowait,  0.0% swap
>> Memory: 2048M real, 80M free, 716M swap in use, 7742M swap free
>>
>>    PID USERNAME LWP PRI NICE  SIZE   RES STATE    TIME    CPU COMMAND
>>  17388 automc     1   0   15  460M  450M cpu/0  320:16 49.99%
>> hit-frequencies
> 
> Is this always the same process?  generating the "overlap" report
> on a big set of logs can take a lot of RAM...

Not sure... 320 minutes seems to be a while though.  I had just noticed
that hit-frequencies had been running for a long time both before and
again after the zone got bounced the other day.  I'm probably just
noticing it running longer now that there's over 2GB of input.

Daryl

Reply via email to