Siju George wrote: > Hi all > > When I run the > > #top > > command in debian it shows all the CPUs cumilatively as shown below. > > top - 06:06:23 up 19 days, 9:33, 6 users, load average: 0.16, 0.41, 1.41 > Tasks: 2166 total, 1 running, 2165 sleeping, 0 stopped, 0 zombie > Cpu(s): 0.6% us, 1.3% sy, 0.0% ni, 98.1% id, 0.0% wa, 0.0% hi, 0.0% si > Mem: 4025604k total, 3741828k used, 283776k free, 375548k buffers > > I have two CPUs and both are working as seen with > > # mpstat -P 0 && mpstat -P 1 > Linux 2.6.8-11-amd64-k8-smp (debian) 01/11/2006 > > 06:08:18 AM CPU %user %nice %system %iowait %irq %soft > %idle intr/s > 06:08:18 AM 0 0.22 0.00 0.04 0.03 0.00 0.00 > 99.71 1011.47 > Linux 2.6.8-11-amd64-k8-smp (debian) 01/11/2006 > > 06:08:18 AM CPU %user %nice %system %iowait %irq %soft > %idle intr/s > 06:08:18 AM 1 0.19 0.00 0.04 0.01 0.00 0.00 > 99.76 0.00 > > > How do I make the top command show CPUs separately as in Redhat? shown below. > > 06:14:11 up 59 days, 18:08, 1 user, load average: 1.10, 0.54, 0.43 > 87 processes: 84 sleeping, 3 running, 0 zombie, 0 stopped > CPU0 states: 38.0% user 7.2% system 0.0% nice 0.0% iowait 53.2% idle > CPU1 states: 49.1% user 4.0% system 0.0% nice 0.0% iowait 46.0% idle > CPU2 states: 10.1% user 2.2% system 0.0% nice 0.0% iowait 86.1% idle > CPU3 states: 9.0% user 0.1% system 0.0% nice 0.0% iowait 90.1% idle > Mem: 4126668k av, 3078548k used, 1048120k free, 0k shrd, 353396k buff > 2521320k actv, 332040k in_d, 14456k in_c > > Thankyou so much :-) > > Kind regards > > Siju > >
FTFM :P Here from 'man top' Summary_Area_defaults 'l' - Load Avg/Uptime On (thus program name) 't' - Task/Cpu states On (1+1 lines, see '1') 'm' - Mem/Swap usage On (2 lines worth) '1' - Single Cpu On (thus 1 line if smp) you need to hit '1' when in top to display it. Then there is another command you can use to save top's settings. I'll leave that as an excercise in manual reading for you ;) -- -------------------------------------------------------------------------------- There's no use in having a dog and doing your own barking. Wednesday Jan 11, 2006 -------------------------------------------------------------------------------- -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]