File: interrupts.htm

package info (click to toggle)
moodss 19.7-1
  • links: PTS
  • area: main
  • in suites: sarge
  • size: 6,136 kB
  • ctags: 3,149
  • sloc: tcl: 49,048; ansic: 187; perl: 178; makefile: 166; sh: 109; python: 65
file content (49 lines) | stat: -rw-r--r-- 3,117 bytes parent folder | download
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
<html>
<head>
<title>interrupts moodss module</title>
</head>
<body>

<p>This is a view of the number and rate of interrupts per IRQ and processor on a Linux machine. 

<p><i><b>Note</b>: more information can be found in the <b>proc</b> manual page and the <b>proc.txt</b> file in the filesystems documentation directory of the kernel source.</i>

<p>The single table columns are:
<ul>
<li>interrupt number, or identification: <i>NMI</i> (Non Maskable Interrupt), <i>LOC</i> (local interrupt counter of the internal APIC) or <i>ERR</i> (incremented in the case of errors in the IO-APIC bus)
<li>corresponding device name if available
<li>interrupt type (for example: <i>XT-PIC</i>, <i>IO-APIC-edge</i>, <i>IO-APIC-level</i>, ...)
<li>absolute interrupts counter for processor number <i>0</i>
<li>interrupts rate (interrupts per second) for processor number <i>0</i>
<li>absolute interrupts counter for processor number <i>1</i> <i>(if present)</i>
<li>interrupts rate (interrupts per second) for processor number <i>1</i> <i>(if present)</i>
<li>...
</ul>

<pre><img src="interrupts.gif"></pre>

<p><b>Module options:</b><ul>
  <li><i>-C</i>&nbsp;&nbsp;&nbsp;<i>(only available for ssh on UNIX client)</i>
  <br>Whether data compression is used on all data between client and server (useful on slow connections, see <i>ssh</i> manual for detailed information).
  <li><i>-i file</i>&nbsp;&nbsp;&nbsp;<i>(only available for ssh on UNIX client)</i>
  <br>Selects a file from which the identity (private key) for authentication is read (useful if an authentication agent is not running). It must not be protected by a passphrase.
  <li><i>-p port</i>&nbsp;&nbsp;&nbsp;<i>(only available for ssh on UNIX client)</i>
  <br>Port to connect to on the remote host.
  <li><i>-r (--remote) [[rsh|ssh]://][user@]host</i>
  <br>remote monitoring using <i>user</i> as logname on remote host <i>host</i> (<i>rsh</i> or <i>ssh</i> facilities must be properly setup). If <i>user</i> is not specified, current user is used as logname on remote host. The protocol is either <i>ssh</i> or <i>rsh</i> (used by default). The module title is set to <i>interrupts(host)</i>.
  <br>When there is a communication error with the remote host, the cells in the <i>count</i> and <i>rate</i> columns are all set to void (displayed as <i>?</i>). A descriptive error message is also generated in such a case.
</ul>

<p><b>Notes on remote monitoring:</b><ul>
  <li>Using <i>ssh</i> is strongly recommended, as <i>rsh</i>, while being much less secure is also less efficient, as it requires creating a new session for each poll.
  <li>On a Windows client, you must use the <i>putty</i> software package (see <i>install.txt</i>), which does not support <i>rsh</i> in non interactive sessions. Consequently, the <i>-r (--remote) ssh://session</i> syntax is required to remove any confusion (where <i>session</i> has been added to the running <i>pageant</i> application).
</ul>

<p><b>Examples:</b>

<pre>$ moodss interrupts -r jdoe@foo.bar.com
$ moodss interrupts -r ssh://jdoe@foo.bar.com
$ moodss interrupts --remote foo.bar.com</pre>

</body>
</html>