Sponsored Content
Top Forums UNIX for Advanced & Expert Users hunting down for software interrupt causes Post 302367004 by fpmurphy on Saturday 31st of October 2009 09:21:36 AM
Old 10-31-2009
Is this just a plain vanilla out-of-the box installation or do you have applications such as Apache, Squid, etc. running on it?
 

7 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

timer interrupt

hello all since a process running in kernel mode cannnot be preempted by any other process what would be the status of Timer interrupt that occurs when the time quantum of a process is elapsed? thanks (2 Replies)
Discussion started by: compbug
2 Replies

2. HP-UX

Hunting Java memory. VSZ? 11.2 and 11.3

We are running into what appears to be a memory leak in java with a program that we are developing. The growth has been confirm on a 12day test. When we look at garbage collection with hpjtune, and jmeter, it appears to releasing the heap memory properly. Does anyone... (1 Reply)
Discussion started by: craigclee
1 Replies

3. Advertise with Us

Job Hunting in Uganda

Hello I am thinking of packing up and moving to Uganda if I can, especially if I can track down some UNIX/Linux type roles there. Broadband has just come ashore in Mombasa and should soon make its way through to UG, I think this is going to trigger a surge in expansion for what is currently a small... (0 Replies)
Discussion started by: steadyonabix
0 Replies

4. UNIX for Advanced & Expert Users

Interrupt storm detected on "irq 20" throttling interrupt source

I receive the following warning messages on a very new machine which has FreeBSD 8.1 x64 installed on it: Interrupt storm detected on "irq 20" throttling interrupt source It is unclear what this means and what its origins are (motherboard? CPU? RAM?). I can start the desktop and the message is... (4 Replies)
Discussion started by: figaro
4 Replies

5. UNIX for Advanced & Expert Users

Is there any shell command to show which interrupt handler handle which interrupt number?

Hi, all: Is there any shell command to show which interrupt handler handle which interrupt number in the system? li,kunlun (5 Replies)
Discussion started by: liklstar
5 Replies

6. What is on Your Mind?

Alarm interrupt and multithreading

Hi Friends any know how became a friend in this Android Programming Language (0 Replies)
Discussion started by: ljarun
0 Replies

7. What is on Your Mind?

Hunting Anomalous Bots - An Introduction to Cyber-Objects - Live From Cyberspace

https://www.unix.com/members/1-albums212-picture687.png Hunting Anomalous Bots - An Introduction to Cyber-Objects - Live From Cyberspace Click title image (above) for video tutorial. (5 Replies)
Discussion started by: Neo
5 Replies
PROCINFO-NG(8)                                                  Linux System Manual                                                 PROCINFO-NG(8)

NAME
procinfo - display system statistics gathered from /proc SYNOPSIS
procinfo [ -fdDSbrhv ] [ -nN ] DESCRIPTION
procinfo gathers some system data from the /proc directory and prints it nicely formatted on the standard output device. The meanings of the fields are as follows: Memory: See the man page for free(1) Bootup: The time the system was booted. Load average: The average number of jobs running, followed by the number of runnable processes and the total number of processes, followed by the PID of the last process run. The pid of the last running process will probably always be procinfo's PID. user: The amount of time spent running jobs in user space. nice: The amount of time spent running niced jobs in user space. system: The amount of time spent running in kernel space. Note: the time spent servicing interrupts is not counted by the kernel (and noth- ing that procinfo can do about it). idle: The amount of time spent doing nothing. uptime: The time that the system has been up. The above four should more or less add up to this one. page in: The number of disk blocks paged into core from disk. 1 block is equal to 1 kiB. page out: The number of disk blocks paged out of core to disk. This includes regular disk-writes. swap in: The number of memory pages paged in from swap. swap out: The number of memory pages paged out to swap. context: The number of context switches, either since bootup or per interval. Disk stats(hda, hdb, sda, sdb): The number of reads and writes made to disks, whether CD-ROM, hard-drive, or USB. Shows all disks if they either are an hdX or sdX, or if they have a non-zero read/write count. Interrupts: Number of interrupts serviced since boot, or per interval, listed per IRQ. OPTIONS
-nN Pause N second between updates. This option implies -f. It may contain a decimal point. The default is 5 seconds. When run by root with a pause of 0 seconds, the program will run at the highest possible priority level. -d For memory, CPU times, paging, swapping, disk, context and interrupt stats, display values per second rather than totals. This option implies -f. -D Same as -d, except that memory stats are displayed as totals. -S When running with -d or -D, always show values per second, even when running with -n N with N greater than one second. -b Display numbers of bytes rather than number of I/O requests. -r This option adds an extra line to the memory info showing 'real' free memory, just as free(1) does. The numbers produced assume that Buffers and Cache are disposable. -H Displays memory stats in 'Human' (base 1024) numbers (KiB, MiB, GiB), instead of implied KBytes. -h Print a brief help message. -v Print version info. INTERACTIVE COMMANDS
When running procinfo fullscreen, you can change its behaviour by pressing d, D, S, r and b, which toggle the flags that correspond to their same-named commandline-options. In addition you can press q which quits the program. FILES
/proc The proc file system. BUGS
All of these statistics are taken verbatim from the kernel, without any scaling. Any case where the kernel specifies that a particular field means something different from how it is documented in this man-page, the kernel always wins. Some features of the original procinfo were elided, as they were considered non-useful, especially as many of them don't change anymore, and have better utilities for listing/displaying them. SEE ALSO
free(1), uptime(1), w(1), init(8), proc(5). AUTHOR
Adam Schrotenboer <adam@tabris.net> v2.0 2007-05-05 PROCINFO-NG(8)
All times are GMT -4. The time now is 02:48 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy