Comment 16 for bug 461141

On 03/03/2011 04:47 PM, Ludovico Cavedon wrote:
> On 03/03/2011 11:55 AM, Justin Cook wrote:
>> This happens to me like clockwork -
>> Fresh start -> 1st suspend ntop goes to 100%
>> I kill the ntop process and I'm fine for all future suspends.
>
> Do you mean that you kill it, restart it (how? "service ntop restart"?),
> and then for future suspends ntop keeps running without going to 100% of
> CPU?

 I kill it with "sudo kill <pid>" and that is it, I don't manually
restart it. I couldn't tell you if ntop is or isn't running after future
suspends, I will look from now on and see.

> So it looks like it only happens for the first suspend after the machine
> boot...
>
> What happens if you do this:
> 1. fresh boot
> 2. stop ntop (service ntop stop)
> 3. suspend
> 4. resume
> 5. start ntop (service ntop start)
> 6. suspend
> 7. resume
>
> Is it going to 100%?

 Give me a bit and I'll attempt this and report back...

>> Package: ntop 3:3.3-13
>
> This version is pretty old and not maintained.
>
> Could you try with version 4.0.3 from
> https://launchpad.net/~cavedon/+archive/ppa
> please?

 I will after I attempt the above.

> Thanks,
> Ludovico
>

much thanks,

Justin