09-22-2003
got my answer. There'a getproc() function that goes with the procinfo struct in procinfo.h.
10 More Discussions You Might Find Interesting
1. Shell Programming and Scripting
I want to know how to work the Co-Processes in kornshell scripts. So, I very need some script about Co-Processes!
thanks ...:) (3 Replies)
Discussion started by: javalee
3 Replies
2. Filesystems, Disks and Memory
write a program create two processes to run a for loop which adds numbers 1 to n , say one process adds odd numbers and other adds even numbers (1 Reply)
Discussion started by: jayaram_miryabb
1 Replies
3. UNIX for Dummies Questions & Answers
Can someone tell how to find out how long a process has been running? I want to find something that is usually there that the paging system can check on.
Thanks (4 Replies)
Discussion started by: Beetlejuice
4 Replies
4. Shell Programming and Scripting
I have a file like this.
No. State Query Times User Processed Syslog
1 ready idle 973s 0 /Application/ugsvols/bldata01/logs/imanscript1562.syslog
2 ready idle 803s 83997 13 /Application/ugsvols/bldata01/logs/imanscript1542.syslog
3 ready idle 2954s 106641... (17 Replies)
Discussion started by: Krrishv
17 Replies
5. UNIX for Dummies Questions & Answers
Hi All,
I am new to unix. Can anyone tell me "How to check the status of the processes running for the current user?"
Regards,
Ravindaran S (1 Reply)
Discussion started by: ravind27
1 Replies
6. UNIX for Advanced & Expert Users
Is there a way to monitor certain processes and if they hang too long to kill them, but certain scripts which are expected to take a long time to let them go?
Thank you
Richard (4 Replies)
Discussion started by: ukndoit
4 Replies
7. Solaris
Hi
Is there an easy way to identify and group currently running processes into OS processes and APP processes. Not all applications are installed as packages.
Any free tools or scripts to do this?
Many thanks. (2 Replies)
Discussion started by: wilsonee
2 Replies
8. Shell Programming and Scripting
Hi All
I was wondering what is the most efficient way to find files in the current directory(that may contain 100,000's files), that meets a certain specified file type and of a certain age.
I have experimented with the find command in unix but it also searches all sub directories. I have... (2 Replies)
Discussion started by: kewong007
2 Replies
9. Programming
Hello All,
Background
========
I am creating a virtual appliance console for a software stack on VMware ESXi. I am using Centos 5.x as the Linux distro (Guest OS). I have created a ncurses based application that does the user authentication and present him with some basic controls to do basic... (2 Replies)
Discussion started by: ku@ntum
2 Replies
10. Shell Programming and Scripting
I had issues with processes locking up. This script checks for processes and kills them if they are older than a certain time.
Its uses some functions you'll need to define or remove, like slog() which I use for logging, and is_running() which checks if this script is already running so you can... (0 Replies)
Discussion started by: sukerman
0 Replies
LSDEV(8) Linux System Manual LSDEV(8)
NAME
lsdev - display information about installed hardware
SYNOPSIS
lsdev
DESCRIPTION
lsdev gathers information about your computer's installed hardware from the interrupts, ioports and dma files in the /proc directory, thus
giving you a quick overview of which hardware uses what I/O addresses and what IRQ and DMA channels.
OPTIONS
None.
FILES
/proc/interrupts
IRQ channels.
/proc/ioports
I/O memory addresses.
/proc/dma
DMA channels.
BUGS
lsdev can't always figure out which lines in the three examined files refer to one and the same device, because these files sometimes use
different names for the same piece of hardware. For example, in some kernels the keyboard is referred to as `kbd' in /proc/ioports and as
`keyboard' in /proc/interrupts. This should be fixed in the kernel, not in lsdev (as has indeed happened for this particular example).
The program does however try to match lines by stripping anything after a space or open parenthesis from the name, so that e.g. the
`serial' lines from /proc/interrupts match the `serial(set)' lines from /proc/ioports. This attempt at DWIM might be considered a bug in
itself.
This program only shows the kernel's idea of what hardware is present, not what's actually physically available.
SEE ALSO
procinfo(8).
AUTHOR
Sander van Malssen <svm@kozmix.cistron.nl>
3rd Release 1998-05-31 LSDEV(8)