01-14-2002
Solaris /proc only has process information ("ls /proc" only shows process numbers). The Linux /proc system has a lot of information about the system such as cpuinfo, meminfo, interrupts used, kernel parameters, etc.
10 More Discussions You Might Find Interesting
1. UNIX for Advanced & Expert Users
my partner change the server's ip address and now i can't to mount the oracle's filesystem, what i do? i don't want to reinstall Unix. My unix is SCO UNIX 5.0.5 (9 Replies)
Discussion started by: marun
9 Replies
2. Shell Programming and Scripting
Hi
How can I only print the file systems that are more than 95% full.
I used the df -k output and tried to check for each file system and then print only the ones that meet the criteria... But my solution seems cloodgie ... (3 Replies)
Discussion started by: YS2002
3 Replies
3. UNIX for Advanced & Expert Users
Dear All
We have HP9000 rp7400 Server running with hp-ux 11i.
Our Disk storage has two volume groups and are allocated as follows:
1. /#vgdisplay -v
--- Volume groups ---
VG Name /dev/vg00
VG Write Access read/write
VG Status available... (1 Reply)
Discussion started by: mhbd
1 Replies
4. AIX
Hi to all
i want to increase the /usr size.
but, it is mirrored on hdisk0 and hdisk1.
i know that chfs will work, but i am not confident about mirroring.
can anyone tell me the procedure.
thanks (2 Replies)
Discussion started by: honeym210
2 Replies
5. UNIX for Dummies Questions & Answers
Hi,
I am trying to calculate the CPU Usage by getting the difference between the idle time reported by /proc/stat at 2 different intervals. Now the 4th entry in the first line of /proc/stat will give me the 'idle time'. But I also came across /proc/uptime that gives me 2 entries : 1st one as the... (0 Replies)
Discussion started by: coderd
0 Replies
6. AIX
hi is that any command to find out which filesystems occupying more process in cpu utilisation (4 Replies)
Discussion started by: senmak
4 Replies
7. UNIX for Dummies Questions & Answers
how to check the record of previously mounted remote filesystems after the filesystems are unmounted .operating system is solaris 10 (0 Replies)
Discussion started by: ravijanjanam12
0 Replies
8. UNIX for Dummies Questions & Answers
hi guys
suse 10.2
today some guys are adding some luns from a SAN so in order to add them I followed this command
echo 1 > /sys/class/fc_host/host1/issue_lip
echo "- - -" > /sys/class/scsi_host/host<number>/scan
nice now
after that I tried to create a folder in /
but it won't let... (2 Replies)
Discussion started by: karlochacon
2 Replies
9. Shell Programming and Scripting
i need to write a shell script for printing the list of filesystems whose disk utilization is more than 75%...i tried using df -h along with awk but cud'nt make the combination work.....:wall:
when we do df -h then the filesystems which are using more than 75% capacity shud be printed according to... (11 Replies)
Discussion started by: xtatic
11 Replies
10. Shell Programming and Scripting
I need a scrip that will show me the filesystems that are greater than 70%...but not sure how to filter using the df -h | grep
Thank you for your help!! (6 Replies)
Discussion started by: eponcedeleonc
6 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)