Re: [9fans] High interruptload on cpu server

[David Presotto <presotto@closedmind.org>]

[-- Attachment #1: Type: text/plain, Size: 253 bytes --]

Depends on what you mean by kill.  Just removing the file from
/rc/bin/service shouldn't be a problem.  Listen will fork and
exec it, and the exec will just die.

Could you just probe one service at a time and see what's fixing
your interrupt load?

[-- Attachment #2: Type: message/rfc822, Size: 2957 bytes --]

From: Matthias Teege <matthias-9fans@mteege.de>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] High interruptload on cpu server
Date: Tue, 25 Nov 2003 14:32:02 +0100
Message-ID: <864qws376f.fsf@gic.mteege.de>

David Presotto <presotto@closedmind.org> writes:

> If you're on a PC, you can look to see how much time is
> spent in interrupts by 'acid -k $pid' and dumping the
> intrtimes array.  Take a look at trap.c and you'll
> understand.  It's just an array of 20 buckets for each

Ok, I'll do so. I discover some nice thing. I can bring down the
interrupt load to a normal level (99% idle ;-)) if I run a nmap
against the cpu server. After the nmap run the interrupt load stays
on that normal level. Maybe I kill a hanging service (timesync?)
whit nmap.

Funny.
Matthias

--
Matthias Teege -- http://www.mteege.de
make world not war