进程系统空闲进程
系统空闲进程 时间:2021-04-10 阅读:()
i目录1进程监控和维护·1-11.
1进程监控和维护命令·1-11.
1.
1displayexceptioncontext1-11.
1.
2displayexceptionfilepath1-51.
1.
3displaykerneldeadloop1-61.
1.
4displaykerneldeadloopconfiguration·1-91.
1.
5displaykernelexception·1-101.
1.
6displayprocess1-131.
1.
7displayprocesscpu·1-151.
1.
8displayprocesslog1-171.
1.
9displayprocessmemory·1-171.
1.
10displayprocessmemoryheap·1-191.
1.
11displayprocessmemoryheapaddress1-201.
1.
12displayprocessmemoryheapsize1-211.
1.
13exceptionfilepath·1-221.
1.
14monitorkerneldeadloopenable1-231.
1.
15monitorkerneldeadloopexclude-thread·1-241.
1.
16monitorkerneldeadlooptime·1-251.
1.
17monitorprocess·1-251.
1.
18monitorthread·1-301.
1.
19processcore1-341.
1.
20resetexceptioncontext1-341.
1.
21resetkerneldeadloop1-351.
1.
22resetkernelexception·1-351-11进程监控和维护1.
1进程监控和维护命令displaymemory、displayprocess、displayprocesscpu、monitorprocess和monitorthread命令既可显示进程的相关信息,又可显示内核线程的相关信息,为简便起见,在这些命令中,统一使用"进程"一词来指代.
1.
1.
1displayexceptioncontextdisplayexceptioncontext命令用来显示进程异常时的上下文信息.
【命令】displayexceptioncontext[countvalue]【视图】任意视图【缺省用户角色】network-admin【参数】countvalue:表示上下文信息的显示个数,取值范围为1~20,缺省值为1.
【使用指导】当进程发生一次异常,系统会生成一个core文件,还会生成一条上下文信息,用于记录异常进程的ID、生成core文件的时间、core文件存放的位置、栈信息和寄存器信息.
一个core文件对应一条上下文信息,最多可记录的上下文信息数和可记录的core文件数目相同.
【举例】#显示在x86体系32位设备上的异常上下文信息.
displayexceptioncontextIndex1of1CrashedPID:120(routed)Crashsignal:SIGBUSCrashtime:TueApr917:14:302013Corefilepath:flash:/core/node0_routed_120_7_20130409-171430_1365527670.
core#00xb7caba4a#10x0804cb79#20xb7cd77c4#30x08049f45Backtracestopped.
Registers'contenteax:0xfffffffcebx:0x00000003ecx:0xbfe244ecedx:0x0000000a1-2esp:0xbfe244b8ebp:0xbfe244c8esi:0xffffffffedi:0xbfe24674eip:0xb7caba4aeflag:0x00000292cs:0x00000073ss:0x0000007bds:0x0000007bes:0x0000007bfs:0x00000000gs:0x00000033#显示在x86体系64位设备上的异常上下文信息.
displayexceptioncontextIndex1of1CrashedPID:121(routed)Crashsignal:SIGBUSCrashtime:SunMar3111:12:212013Corefilepath:flash:/core/node0_routed_121_7_20130331-111221_1364728341.
core#00x00007fae7dbad20c#10x00000000004059fa#20x00007fae7dbd96c0#30x0000000000402b29Backtracestopped.
Registers'contentrax:0xfffffffffffffffcrbx:0x00007fff88a5dd10rcx:0xffffffffffffffffrdx:0x000000000000000arsi:0x00007fff88a5dd10rdi:0x0000000000000003rbp:0x00007fff88a5dcf0rsp:0x00007fff88a5dcf0r8:0x00007fae7ea587e0r9:0x0000000000000079r10:0xffffffffffffffffr11:0x0000000000000246r12:0x0000000000405b18r13:0x00007fff88a5ff7ar14:0x00007fff88a5de30r15:0x0000000000000000rip:0x00007fae7dbad20cflag:0x0000000000000246cs:0x0000000000000033ss:0x000000000000002bds:0x0000000000000000es:0x0000000000000000fs:0x0000000000000000gs:0x0000000000000000fs_base:0x00007fae80a5d6a0gs_base:0x0000000000000000orig_ax:0x00000000000000e8#显示在powerpc体系32位设备上的异常上下文信息.
displayexceptioncontextIndex1of1CrashedPID:133(routed)Crashsignal:SIGBUSCrashtime:WedApr1015:47:492013Corefilepath:flash:/core/node0_routed_133_7_20130410-154749_1365608869.
core#00x184720bc#10x10006b4cBacktracestopped.
Registers'contentgrp00:0x000000ee0x7ffd6ad00x1800f4400x00000004grp04:0x7ffd6af80x0000000a0xffffffff0x184720bcgrp08:0x0002d2000x000000030x000000010x1847209c1-3grp12:0x10006b4c0x100205340xd67441000x00000000grp16:0x000000000xa0203ff00xa028b12c0xa028b13cgrp20:0xa028b1480xa028b1680xa028b1780xa028b190grp24:0xa028b1a80xa028b1b80x000000000x7ffd6c08grp28:0x10006cac0x7ffd6f920x184c1b840x7ffd6ae0nip:0x184720bclr:0x10006b4ccr:0x38000022ctr:0x1847209cmsr:0x0002db00xer:0x00000000ret:0xfffffffcdsisr:0x08000000gr3:0x00000003mq:0x00000000trap:0x00000c00dar:0x1833114c#显示在powerpc体系64位设备上的异常上下文信息.
displayexceptioncontextIndex1of1CrashedPID:172(routed)Crashsignal:SIGBUSCrashtime:SatSep1516:53:162007Corefilepath:cfa0:/core/node1_routed_172_7_20070915-165316_1189875196.
core#00x00000fff803c66b4#10x0000000010009b94#20x00000fff80401814Backtracestopped.
Registers'contentgrp00:0x00000000000000ee0x00000fffffd04840grp02:0x00000fff80425c280x0000000000000004grp04:0x00000fffffd048c00x000000000000000agrp06:0xffffffffffffffff0x00000fff803c66b4grp08:0x000000008002d0000x0000000000000000grp10:0x00000000000000000x0000000000000000grp12:0x00000000000000000x00000fff80a096b0grp14:0x000000007b964c000x000000007b7d0000grp16:0x00000000000000010x000000000000000bgrp18:0x00000000000000310x0000000000a205b8grp20:0x0000000000a206770x0000000000000000grp22:0x000000007bb910140x0000000000000000grp24:0xc0000000005ae1c80x0000000000000000grp26:0xc0000001f00bff200xc0000001f00b0000grp28:0x00000fffffd04a300x000000001001aed8grp30:0x00000fffffd04fae0x00000fffffd04840nip:0x00000fff803c66b4lr:0x0000000010009b94cr:0x0000000058000482ctr:0x00000fff803c66acmsr:0x000000008002d000xer:0x0000000000000000ret:0xfffffffffffffffcdsisr:0x0000000000000000gr3:0x0000000000000003softe:0x0000000000000001trap:0x0000000000000c00dar:0x00000fff8059d14c#显示在mips体系32位设备上的异常上下文信息.
displayexceptioncontext1-4Index1of1CrashedPID:182(routed)Crashsignal:SIGBUSCrashtime:SunJan208:11:382013Corefilepath:flash:/core/node4_routed_182_10_20130102-081138_1293955898.
core#00x2af2faf4#10x00406d8cBacktracestopped.
Registers'contentzero:0x00000000at:0x1000dc00v0:0x00000004v1:0x00000003a0:0x00000003a1:0x7fd267e8a2:0x0000000aa3:0x00000001t0:0x00000000t1:0xcf08fa14t2:0x80230510t3:0xfffffff8t4:0x69766520t5:0x00000000t6:0x63cc6000t7:0x44617461s0:0x7fd26f81s1:0x00401948s2:0x7fd268f8s3:0x803e1db0s4:0x803e1da0s5:0x803e1d88s6:0x803e1d70s7:0x803e1d60t8:0x00000008t9:0x2af2fae0k0:0x00000000k1:0x00000000gp:0x2af9a3a0sp:0x7fd267c0s8:0x7fd267c0ra:0x00406d8csr:0x0000dc13lo:0xef9db265hi:0x0000003fbad:0x2add2010cause:0x00800020pc:0x2af2faf4#显示在mips体系64位设备上的异常上下文信息.
displayexceptioncontextIndex1of1CrashedPID:270(routed)Crashsignal:SIGBUSCrashtime:WedMar2712:39:122013Corefilepath:flash:/core/node16_routed_270_10_20130327-123912_1364387952.
core#00x0000005555a3bcb4#10x0000000120006c1cBacktracestopped.
Registers'contentzero:0x0000000000000000at:0x0000000000000014v0:0x0000000000000004v1:0x0000000000000003a0:0x0000000000000003a1:0x000000ffff899d90a2:0x000000000000000aa3:0x0000000000000001a4:0x0000005555a9b4e0a5:0x0000000000000000a6:0xffffffff8021349ca7:0x20696e206368616et0:0x0000000000000000t1:0xffffffff80105068t2:0xffffffff80213890t3:0x0000000000000008s0:0x0000005555a99c40s1:0x000000ffff89af5fs2:0x0000000120007320s3:0x0000005555a5f470s4:0x000000ffff899f80s5:0xffffffff803cc6c0s6:0xffffffff803cc6a8s7:0xffffffff803cc690t8:0x0000000000000002t9:0x0000005555a3bc98k0:0x0000000000000000k1:0x00000000000000001-5gp:0x0000000120020460sp:0x000000ffff899d70s8:0x000000ffff899d80ra:0x0000000120006c1csr:0x000000000400fff3lo:0xdf3b645a1cac08c9hi:0x000000000000007fbad:0x000000555589ba84cause:0x0000000000800020pc:0x0000005555a3bcb4表1-1displayexceptioncontext命令输出信息描述表字段描述CrashedPID发生异常的进程IDCrashsignal导致异常的信号:SIGABRT:异常终止(abort)SIGBUS:总线错误SIGFPE:浮点异常SIGILL:程序执行了非法指令,导致异常SIGQUIT:终端退出符SIGSEGV:无效存储访问SIGSYS:无效系统调用SIGTRAP:跟踪断点时发生了异常SIGXCPU:超过CPU限制(setrlimit)SIGXFSZ:超过文件长度限制(setrlimit)SIGUNKNOW:未知原因Crashtime异常发生的时间Corefilepathcore文件存放的位置Backtracestopped表示栈信息已经显示完毕Registers'content寄存器的内容【相关命令】resetexceptioncontext1.
1.
2displayexceptionfilepathdisplayexceptionfilepath命令用来显示core文件的保存路径.
【命令】displayexceptionfilepath【视图】任意视图【缺省用户角色】network-admin1-6【举例】#显示主控板上core文件的保存路径.
displayexceptionfilepathTheexceptionfilepathisflash:.
1.
1.
3displaykerneldeadloopdisplaykerneldeadloop命令用来显示内核线程死循环信息.
【命令】displaykerneldeadloopshow-number[offset][verbose]【视图】任意视图【缺省用户角色】network-admin【参数】show-number:需要显示的死循环信息的数目,取值范围为1~20.
offset:需要显示的起始条目距最近条目的偏移,取值范围为0~19,缺省值为0.
verbose:表示显示详细信息.
不指定该参数时,显示概要信息.
【举例】#显示最近一条内核线程死循环的概要信息.
displaykerneldeadloop1Deadlooprecord1Description:BUG:softlockup-CPU#0stuckfor61!
[comsh:16306]Recordedat:2013-05-0111:16:00.
823018Occurredat:2013-05-0111:16:00.
823018Instructionaddress:0x4004158cThread:comsh(TID:16306)Context:threadcontextChassis:0Slot:0CPUID:0Kernelmoduleinfo:modulename(mrpnc)moduleaddress(0xe332a000)modulename(12500)moduleaddress(0xe00bd000)#显示最近一条内核线程死循环的详细信息.
displaykerneldeadloop1verboseDeadlooprecord1Description:BUG:softlockup-CPU#0stuckfor61!
[comsh:16306]Recordedat:2013-05-0111:16:00.
823018Occurredat:2013-05-0111:16:00.
823018Instructionaddress:0x4004158cThread:comsh(TID:16306)Context:threadcontextChassis:01-7Slot:0CPUID:0Kernelmoduleinfo:modulename(mrpnc)moduleaddress(0xe332a000)modulename(12500)moduleaddress(0xe00bd000)Last5threadswitches:migration/0(11:16:00.
823018)-->swapper(11:16:00.
833018)-->kthreadd(11:16:00.
833518)-->swapper(11:16:00.
833550)-->disk(11:16:00.
833560)Registercontent:Reg:r0,Val=0x00000000;Reg:r1,Val=0xe2be5ea0;Reg:r2,Val=0x00000000;Reg:r3,Val=0x77777777;Reg:r4,Val=0x00000000;Reg:r5,Val=0x00001492;Reg:r6,Val=0x00000000;Reg:r7,Val=0x0000ffff;Reg:r8,Val=0x77777777;Reg:r9,Val=0x00000000;Reg:r10,Val=0x00000001;Reg:r11,Val=0x0000002c;Reg:r12,Val=0x057d9484;Reg:r13,Val=0x00000000;Reg:r14,Val=0x00000000;Reg:r15,Val=0x02000000;Reg:r16,Val=0xe2be5f00;Reg:r17,Val=0x00000000;Reg:r18,Val=0x00000000;Reg:r19,Val=0x00000000;Reg:r20,Val=0x024c10f8;Reg:r21,Val=0x057d9244;Reg:r22,Val=0x00002000;Reg:r23,Val=0x0000002c;Reg:r24,Val=0x00000002;Reg:r25,Val=0x24000024;Reg:r26,Val=0x00000000;Reg:r27,Val=0x057d9484;Reg:r28,Val=0x0000002c;Reg:r29,Val=0x00000000;Reg:r30,Val=0x0000002c;Reg:r31,Val=0x00000000;Reg:cr,Val=0x84000028;Reg:nip,Val=0x057d9550;Reg:xer,Val=0x00000000;Reg:lr,Val=0x0186eff0;Reg:ctr,Val=0x682f7344;Reg:msr,Val=0x00784b5c;Reg:trap,Val=0x0000b030;Reg:dar,Val=0x77777777;Reg:dsisr,Val=0x40000000;Reg:result,Val=0x00020300;Dumpstack(total1024bytes,16bytes/line):0xe2be5ea0:02be5ec02400002400000000057d94840xe2be5eb0:000000040000000000000028058d34c40xe2be5ec0:02be60a00186eff000000000000000000xe2be5ed0:020405b40000000000000000000000000xe2be5ee0:000000000000000000000000000000000xe2be5ef0:954773350000000000000000000000000xe2be5f00:a0e164210000000000000000000000000xe2be5f10:00000000000000000000000001e900000xe2be5f20:000000000000000000000000000000000xe2be5f30:000000000000000002be66c002be66d00xe2be5f40:02be61e000000002000000000244b3a40xe2be5f50:02be5f900000000802be5fe0000000080xe2be5f60:02be5f8000ac1b1400000000000000001-80xe2be5f70:05b45f9002be5fe00000003002be5fe00xe2be5f80:02be5fc000ac1bf400000000024500000xe2be5f90:000300000000000002be5fe0000000300xe2be5fa0:02be5fc000ac1b1461f12eae024500000xe2be5fb0:0244b37402be5fd00000003002be5fe00xe2be5fc0:02be60600174fff800000000000008000xe2be5fd0:02be5ff000e8937e02be5ff802be5ffc0xe2be5fe0:00000000000000000000000002be60180xe2be5ff0:02be601000e965980000005800002a4f0xe2be6000:02be6010000000000000000002be60680xe2be6010:02be604000e8c6a000001117000000000xe2be6020:02be6040000000000000000002be60980xe2be6030:02270000000000000000000002be60680xe2be6040:02be6060000000010000b03002be60980xe2be6050:00000004022100000000000001e900000xe2be6060:000000000000000000000000000000000xe2be6070:000000000000000002be66c002be66d00xe2be6080:02be61e0000000020000000002be61700xe2be6090:0000000002210000058d34c4057d9244Calltrace:FunctionAddress=0x8012a4b4FunctionAddress=0x8017989cFunctionAddress=0x80179b30FunctionAddress=0x80127438FunctionAddress=0x8012d734FunctionAddress=0x80100a00FunctionAddress=0xe0071004FunctionAddress=0x8016ce0cFunctionAddress=0x801223a0Instructiondump:41a2fe9c812300ec800200ec7f890000409efe8c80010014540b07b940a2fe804bfffe6c807802907f64db784804ea353880000038a000803863000c表1-2displaykerneldeadloop命令显示信息描述表字段描述Description发生死循环的内核线程的描述信息,包括死循环内核线程所在的CPU的编号、内核线程连续运行的时间、内核线程的名称和编号Recordedat内核线程死循环被记录到主控板上的时间点,精确到微秒Occurredat内核线程发生死循环的时间,精确到微秒Instructionaddress内核线程被检测到发生死循环时对应的指令信息Thread发生死循环的内核线程的名称和编号Context内核线程被检测到发生死循环时所在的上下文环境Slot为固定值0,无特殊意义(集中式设备)1-9字段描述CPUID运行该内核线程的CPU的编号Kernelmoduleinfo内核线程被检测到发生死循环时,系统中已加载的内核模块信息.
包括内核模块名和内核模块加载的内存地址Last5threadswitches内核线程被检测到发生死循环时,记录死循环发生的CPU上、最近五次的内核线程切换轨迹.
包括内核线程的名称和内核线程切换时间点,时间精确到微秒Registercontent内核线程被检测到发生死循环时现场的寄存器信息.
Reg表示寄存器名称,Val表示寄存器中保存的值Dumpstack内核线程被检测到发生死循环时现场的堆栈信息Calltrace内核线程被检测到发生死循环时现场的函数调用栈信息,即每级调用函数的指令地址Instructiondump内核线程被检测到发生死循环时对应的指令码.
非法指令用ffffffff表示Noinformationtodisplay表示系统中没有内核线程死循环记录【相关命令】resetkerneldeadloop1.
1.
4displaykerneldeadloopconfigurationdisplaykerneldeadloopconfiguration命令用来显示内核线程死循环监控参数配置.
【命令】displaykerneldeadloopconfiguration【视图】任意视图【缺省用户角色】network-admin【举例】#显示内核线程死循环监控参数配置.
displaykerneldeadloopconfigurationThreaddeadloopdetection:EnabledDeadlooptimer(inseconds):60Threadsexcludedfrommonitoring:1TID:15Name:co0表1-3displaykerneldeadloopconfiguration命令显示信息描述表字段描述Threaddeadloopdetection:Enabled内核线程死循环检测功能处于开启状态Threaddeadloopdetection:Disabled内核线程死循环检测功能处于关闭状态1-10字段描述Deadlooptimer(inseconds):n内核线程死循环判定周期(单位为秒),即内核线程连续运行时间大于n秒时,则判定为死循环Threadsexcludedfrommonitoring不进行死循环检测的内核线程列表,配置monitorkerneldeadloopexclude-thread命令后才会显示该信息Name不进行死循环检测的内核线程的名称TID不进行死循环检测的内核线程的编号Nothreadisexcludedfrommonitoring对所有内核线程都进行死循环检查1.
1.
5displaykernelexceptiondisplaykernelexception命令用来显示内核线程的异常信息.
【命令】displaykernelexceptionshow-number[offset][verbose]【视图】任意视图【缺省用户角色】network-admin【参数】show-number:需要显示的异常信息的数目,取值范围为1~20.
offset:开始显示的条目距最近条目的偏移,取值范围为0~19,缺省值为0.
verbose:显示详细信息.
不指定该参数时,显示概要信息.
【使用指导】当内核线程在运行过程中发生异常时,系统会自动记录异常信息,以便设备维护人员定位问题.
【举例】#显示最近一条内核线程异常的概要信息.
displaykernelexception1Exceptionrecord1Description:Oops[#0]Recordedat:2013-05-0111:16:00.
823018Occurredat:2013-05-0111:16:00.
823018Instructionaddress:0x4004158cThread:comsh(TID:16306)Context:threadcontextChassis:0Slot:0CPUID:0Kernelmoduleinfo:modulename(mrpnc)moduleaddress(0xe332a000)modulename(disk)moduleaddress(0xe00bd000)1-11#显示最近一条内核线程异常的详细信息.
displaykernelexception1verboseExceptionrecord1Description:Oops[#0]Recordedat:2013-05-0111:16:00.
823018Occurredat:2013-05-0111:16:00.
823018Instructionaddress:0x4004158cThread:comsh(TID:16306)Context:threadcontextChassis:0Slot:0CPUID:0Kernelmoduleinfo:modulename(mrpnc)moduleaddress(0xe332a000)modulename(12500)moduleaddress(0xe00bd000)Last5threadswitches:migration/0(11:16:00.
823018)-->swapper(11:16:00.
833018)-->kthreadd(11:16:00.
833518)-->swapper(11:16:00.
833550)-->disk(11:16:00.
833560)Registercontent:Reg:r0,Val=0x00000000;Reg:r1,Val=0xe2be5ea0;Reg:r2,Val=0x00000000;Reg:r3,Val=0x77777777;Reg:r4,Val=0x00000000;Reg:r5,Val=0x00001492;Reg:r6,Val=0x00000000;Reg:r7,Val=0x0000ffff;Reg:r8,Val=0x77777777;Reg:r9,Val=0x00000000;Reg:r10,Val=0x00000001;Reg:r11,Val=0x0000002c;Reg:r12,Val=0x057d9484;Reg:r13,Val=0x00000000;Reg:r14,Val=0x00000000;Reg:r15,Val=0x02000000;Reg:r16,Val=0xe2be5f00;Reg:r17,Val=0x00000000;Reg:r18,Val=0x00000000;Reg:r19,Val=0x00000000;Reg:r20,Val=0x024c10f8;Reg:r21,Val=0x057d9244;Reg:r22,Val=0x00002000;Reg:r23,Val=0x0000002c;Reg:r24,Val=0x00000002;Reg:r25,Val=0x24000024;Reg:r26,Val=0x00000000;Reg:r27,Val=0x057d9484;Reg:r28,Val=0x0000002c;Reg:r29,Val=0x00000000;Reg:r30,Val=0x0000002c;Reg:r31,Val=0x00000000;Reg:cr,Val=0x84000028;Reg:nip,Val=0x057d9550;Reg:xer,Val=0x00000000;Reg:lr,Val=0x0186eff0;Reg:ctr,Val=0x682f7344;Reg:msr,Val=0x00784b5c;Reg:trap,Val=0x0000b030;Reg:dar,Val=0x77777777;Reg:dsisr,Val=0x40000000;Reg:result,Val=0x00020300;Dumpstack(total1024bytes,16bytes/line):0xe2be5ea0:02be5ec02400002400000000057d94840xe2be5eb0:000000040000000000000028058d34c40xe2be5ec0:02be60a00186eff000000000000000001-120xe2be5ed0:020405b40000000000000000000000000xe2be5ee0:000000000000000000000000000000000xe2be5ef0:954773350000000000000000000000000xe2be5f00:a0e164210000000000000000000000000xe2be5f10:00000000000000000000000001e900000xe2be5f20:000000000000000000000000000000000xe2be5f30:000000000000000002be66c002be66d00xe2be5f40:02be61e000000002000000000244b3a40xe2be5f50:02be5f900000000802be5fe0000000080xe2be5f60:02be5f8000ac1b1400000000000000000xe2be5f70:05b45f9002be5fe00000003002be5fe00xe2be5f80:02be5fc000ac1bf400000000024500000xe2be5f90:000300000000000002be5fe0000000300xe2be5fa0:02be5fc000ac1b1461f12eae024500000xe2be5fb0:0244b37402be5fd00000003002be5fe00xe2be5fc0:02be60600174fff800000000000008000xe2be5fd0:02be5ff000e8937e02be5ff802be5ffc0xe2be5fe0:00000000000000000000000002be60180xe2be5ff0:02be601000e965980000005800002a4f0xe2be6000:02be6010000000000000000002be60680xe2be6010:02be604000e8c6a000001117000000000xe2be6020:02be6040000000000000000002be60980xe2be6030:02270000000000000000000002be60680xe2be6040:02be6060000000010000b03002be60980xe2be6050:00000004022100000000000001e900000xe2be6060:000000000000000000000000000000000xe2be6070:000000000000000002be66c002be66d00xe2be6080:02be61e0000000020000000002be61700xe2be6090:0000000002210000058d34c4057d9244Calltrace:FunctionAddress=0x8012a4b4FunctionAddress=0x8017989cFunctionAddress=0x80179b30FunctionAddress=0x80127438FunctionAddress=0x8012d734FunctionAddress=0x80100a00FunctionAddress=0xe0071004FunctionAddress=0x8016ce0cFunctionAddress=0x801223a0Instructiondump:41a2fe9c812300ec800200ec7f890000409efe8c80010014540b07b940a2fe804bfffe6c807802907f64db784804ea353880000038a000803863000c本命令显示信息的详细描述请参见表1-2.
【相关命令】resetkernelexception1-131.
1.
6displayprocessdisplayprocess命令用来显示进程的状态信息.
【命令】displayprocess[all|jobjob-id|nameprocess-name]【视图】任意视图【缺省用户角色】network-adminnetwork-operator【参数】all:显示所有进程的状态信息.
指定all参数和不指定任何可选参数时,命令行的执行效果相同.
jobjob-id:任务编号,用于唯一标识一个进程,该编号不会随着进程的重启而改变,取值范围为1~2147483647.
nameprocess-name:进程名称,为1~15个字符的字符串,不区分大小写,不能包含问号和空格.
【举例】#显示进程scmd的状态信息.
displayprocessnamescmdJobID:1PID:1ParentJID:0ParentPID:0Executablepath:-Instance:0Respawn:OFFRespawncount:1Max.
spawnsperminute:0Laststarted:WedJun114:45:462013Processstate:sleepingMax.
core:0ARGS:-TIDLAST_CPUStackPRIStateHH:MM:SS:MSECName100K120S0:0:5:220scmd表1-4displayprocessname命令显示信息描述表字段描述JobID任务编号,用于唯一标识一个进程,该编号不会随着进程的重启而改变PID进程编号,用于标识一个进程,但该编号可能会随着进程的重启而改变ParentJID父进程的任务编号ParentPID父进程的进程编号Executablepath进程执行路径(内核线程执行路径显示为"-")1-14字段描述Instance进程的实例号(一个进程根据需要在软件实现时决定了它是否会运行多个实例)Respawn运行出错时,该进程是否会自动重启:ON表示自动重启OFF表示不自动重启Respawncount进程重启的次数(初始值为1)Max.
spawnsperminute进程一分钟内允许异常重启的最大次数(如果进程在一分钟内异常重启次数超过该值,则系统会自动关闭该进程)Laststarted进程最近一次启动的日期和时间Processstate进程状态,可能的取值为:running:运行状态或正在队列中等待调度sleeping:可中断睡眠状态tracedorstopped:暂停状态uninterruptiblesleep:不可中断睡眠状态zombie:僵死状态(僵死状态指的是进程已经退出,但是仍然占用部分资源的状态)Max.
core进程最多可以生成的core文件的数量,如果为0表示不生成core文件(进程异常重启一次,会产生一个core文件.
如果生成的core文件的数目达到最大值,则不再生成core文件.
软件开发和维护人员能够根据core文件的内容来定位异常的原因和异常的位置)ARGS进程启动时携带的参数.
如果进程不带参数,显示为"-"TID线程编号LAST_CPU进程最近一次被调度时,所在的CPUStack堆栈大小PRI线程优先级State线程状态,可能的取值为:R:running,运行状态或正在队列中等待调度S:sleeping,可中断睡眠状态T:tracedorstopped,暂停状态D:uninterruptiblesleep,不可中断睡眠状态Z:zombie,僵死状态HH:MM:SS:MSEC进程最近一次启动后的运行时间Name进程名称#显示所有进程的状态信息.
displayprocessallJIDPID%CPU%MEMSTATPRITTYHH:MM:SSCOMMAND110.
00.
0S120-00:00:04scmd220.
00.
0S115-00:00:00[kthreadd]1-15330.
00.
0S99-00:00:00[migration/0]440.
00.
0S115-00:00:05[ksoftirqd/0]550.
00.
0S99-00:00:00[watchdog/0]660.
00.
0S115-00:00:00[events/0]770.
00.
0S115-00:00:00[khelper]880.
00.
0S115-00:00:00[kblockd/0]990.
00.
0S115-00:00:00[ata/0]10100.
00.
0S115-00:00:00[ata_aux]11110.
00.
0S115-00:00:00[kseriod]12120.
00.
0S120-00:00:00[vzmond]13130.
00.
0S120-00:00:00[pdflush]14140.
00.
0S120-00:00:00[pdflush]15150.
00.
0S115-00:00:00[kswapd0]16160.
00.
0S115-00:00:00[aio/0]17170.
00.
0S115-00:00:00[scsi_eh_0]18180.
00.
0S115-00:00:00[scsi_eh_1]19190.
00.
0S115-00:00:00[scsi_eh_2]35350.
00.
0D100-00:00:00[lipc_topology]----More----表1-5displayprocessall命令显示信息描述字段描述JID任务编号,用于唯一标识一个进程,该编号不会随着进程的重启而改变PID进程编号%CPUCPU使用率(用百分比表示)%MEM内存使用率(用百分比表示)STAT进程状态,可能的取值为:R:running,运行状态或处于运行队列S:sleeping,可中断睡眠状态T:tracedorstopped,暂停状态D:uninterruptiblesleep,不可中断睡眠状态Z:zombie,僵死状态PRI进程优先级(优先级在进程调度时发挥作用,优先级高的会优先得到调度)TTY进程使用的终端HH:MM:SS进程最近一次启动后的运行时间COMMAND进程名称以及进程运行的参数(如果进程名称带有"[]"标记,则表示内核线程)1.
1.
7displayprocesscpudisplayprocesscpu命令用来显示所有进程的CPU使用率信息.
【命令】displayprocesscpu1-16【视图】任意视图【缺省用户角色】network-adminnetwork-operator【举例】#显示所有进程CPU使用率信息.
displayprocesscpuCPUutilizationin5secs:16.
8%;1min:4.
7%;5mins:4.
7%JID5Sec1Min5MinName10.
0%0.
0%0.
0%scmd20.
0%0.
0%0.
0%[kthreadd]30.
1%0.
0%0.
0%[ksoftirqd/0]40.
0%0.
0%0.
0%[watchdog/0]50.
0%0.
0%0.
0%[events/0]60.
0%0.
0%0.
0%[khelper]290.
0%0.
0%0.
0%[kblockd/0]490.
0%0.
0%0.
0%[vzmond]520.
0%0.
0%0.
0%[pdflush]530.
0%0.
0%0.
0%[pdflush]540.
0%0.
0%0.
0%[kswapd0]1100.
0%0.
0%0.
0%[aio/0]7120.
0%0.
0%0.
0%[mtdblockd]7190.
0%0.
0%0.
0%[TNetJob]7200.
0%0.
0%0.
0%[TMTH]7270.
0%0.
0%0.
0%[CF]7300.
0%0.
0%0.
0%[DIBC]7520.
0%0.
0%0.
0%[lipc_topology]7620.
0%0.
0%0.
0%[MNET]7630.
0%0.
0%0.
0%[SYSM]----More----表1-6displayprocesscpu命令显示信息描述表字段描述CPUutilizationin5secs:16.
8%;1min:4.
7%;5mins:4.
7%系统最近5秒CPU使用率;最近1分钟CPU使用率;最近5分钟CPU使用率JID任务编号(用于唯一标识一个进程,该编号不会随着进程的重启而改变)5Sec最近5秒钟内进程的CPU使用率1Min最近1分钟内进程的CPU使用率5Min最近5分钟内进程的CPU使用率Name进程名称(如果进程名称带有"[]"标记,则表示该进程为内核线程)1-171.
1.
8displayprocesslogdisplayprocesslog命令用来显示所有进程的日志信息.
【命令】displayprocesslog【视图】任意视图【缺省用户角色】network-adminnetwork-operator【举例】#显示所有进程的日志信息.
displayprocesslogNameJIDPIDAbortCoreStart-timeEnd-timemdcd135135NN2013-06-1109:31:002013-06-1109:31:00knotify156156NN2013-06-1109:31:022013-06-1109:31:02knotify158158NN2013-06-1109:31:022013-06-1109:31:02knotify195195NN2013-06-1109:31:032013-06-1109:31:03pkg_update203203NN2013-06-1109:31:062013-06-1109:31:06autocfgd219219NN2013-06-1109:31:132013-06-1109:31:13comsh202202NN2013-06-1109:31:052013-06-1109:31:13表1-7displayprocesslog命令显示信息描述表字段描述Name进程名JID进程任务编号PID进程编号Abort是否异常退出:Y表示异常退出N表示正常退出Core是否产生core文件Y表示产生N表示未产生Start-time进程创建时间End-time进程结束时间1.
1.
9displayprocessmemorydisplayprocessmemory命令用来显示所有进程的代码段、数据段以及堆栈等的内存使用信息.
1-18【命令】displayprocessmemory【视图】任意视图【缺省用户角色】network-adminnetwork-operator【使用指导】进程启动时,会向系统申请Text、Data、Stack和Dynamic类型的内存.
Text类型的内存用来存放进程的代码.
Data类型的内存用来存放进程的数据.
Stack内存指的是栈内存,一般存放临时数据.
Dynamic类型的内存指的是堆内存(heap),由系统根据进程运行需要进行动态分配(malloc)和释放(free),可使用displayprocessmemoryheap命令显示Dynamic类型内存的详细信息.
【举例】#显示所有进程的内存使用信息.
displayprocessmemoryJIDTextDataStackDynamicName138418001636scmd20000[kthreadd]30000[ksoftirqd/0]40000[watchdog/0]50000[events/0]60000[khelper]290000[kblockd/0]490000[vzmond]520000[pdflush]----More----表1-8displayprocessmemory命令显示信息描述表字段描述JID任务编号.
用于唯一标识一个进程,该编号不会随着进程的重启而改变Text进程占用的代码段大小,单位为KB(内核线程该项大小为0)Data进程占用的数据段大小,单位为KB(内核线程该项大小为0)Stack进程占用的堆栈大小,单位为KB(内核线程该项大小为0)Dynamic进程动态申请内存大小,单位为KB(内核线程该项大小为0)Name进程名称(如果进程名称带有"[]"标记,则表示该进程为内核线程)1-19【相关命令】displayprocessmemoryheapdisplayprocessmemoryheapaddressdisplayprocessmemoryheapsize1.
1.
10displayprocessmemoryheapdisplayprocessmemoryheap命令用来显示指定进程的堆内存统计信息.
【命令】displayprocessmemoryheapjobjob-id[verbose]【视图】任意视图【缺省用户角色】network-adminnetwork-operator【参数】jobjob-id:任务编号,用于唯一标识一个进程,该编号不会随着进程的重启而改变.
取值范围为1~2147483647.
verbose:显示内存详细统计信息.
不指定该参数时,显示内存概要统计信息.
【使用指导】系统的堆内存由固定大小(比如size=16字节、size=64字节等)的内存块构成,用于存放进程运行过程中需要用到的数据或者中间变量.
当进程启动时,系统会根据进程运行需要,给进程动态分配堆内存.
进程的堆内存信息可使用displayprocessmemoryheap命令显示.
每个内存块都有地址,该地址用十六进制数表示,可通过displayprocessmemoryheapsize命令显示.
用户使用内存块的地址可以访问内存块,获取内存块的内容,内存块的内容可通过displayprocessmemoryheapaddress命令显示.
【举例】#显示job148的堆内存概要统计信息.
displayprocessmemoryheapjob148Totalvirtualmemoryheapspace(inbytes):2228224Totalphysicalmemoryheapspace(inbytes):262144Totalallocatedmemory(inbytes):161576#显示job148的堆内存详细统计信息.
displayprocessmemoryheapjob148verboseHeapusage:SizeFreeUsedTotalFreeRatio168526013%643126212650.
2%12822072091%512355585.
1%409632973001%1-208192119205%819200110%Summary:Totalvirtualmemoryheapspace(inbytes):2293760Totalphysicalmemoryheapspace(inbytes):58368Totalallocatedmemory(inbytes):42368以上显示信息表明:job148分得size大小16字节的内存块60个(已用52个,还有8个未使用),size大小为64字节的内存块1265个(已用1262个,还有3个未使用),以此类推.
表1-9displayprocessmemoryheap命令显示信息描述表命令字功能描述Totalvirtualmemoryheapspace(inbytes)虚拟堆内存总大小,单位为字节Totalphysicalmemoryheapspace(inbytes)物理堆内存总大小,单位为字节Totalallocatedmemory(inbytes)任务已使用的堆内存大小,单位为字节Size内存块大小,单位为字节Free空闲的内存块个数Used已使用的内存块个数Total指定大小内存块总个数,为Free和Used之和FreeRatioFree与Total的比率,可以反映这种大小内存块的碎片情况【相关命令】displayprocessmemorydisplayprocessmemoryheapaddressdisplayprocessmemoryheapsize1.
1.
11displayprocessmemoryheapaddressdisplayprocessmemoryheapaddress命令用来显示从指定地址开始的内存空间的内容.
【命令】displayprocessmemoryheapjobjob-idaddressstarting-addresslengthmemory-length【视图】任意视图【缺省用户角色】network-adminnetwork-operator1-21【参数】jobjob-id:任务编号,用于唯一标识一个进程,该编号不会随着进程的重启而改变,取值范围为1~2147483647.
addressstarting-address:内存块的起始地址.
lengthmemory-length:内存的长度,取值范围为1~1024,单位为字节.
【使用指导】当进程运行异常时,使用该命令可以帮助设备维护人员诊断和定位问题.
【举例】#显示job1从地址0xb7e30580开始,长度为128字节的内存空间的内容.
displayprocessmemoryheapjob1addressb7e30580length128B7E30580:1400EFFF00000000E439E2B77C05E3B79.
.
|.
.
.
B7E30590:1400EFFF2F7362696E2F736C62676400.
.
.
.
/sbin/slbgd.
B7E305A0:1400EFFF00000000443BE2B78C05E3B7.
.
.
.
.
.
.
.
D;.
.
.
.
.
.
B7E305B0:1400EFFF2F7362696E2F6F7370666400.
.
.
.
/sbin/ospfd.
B7E305C0:1400EFFF00000000A43CE2B7AC05E3B7B7E305D0:1400EFFF2F7362696E2F6D7374706400.
.
.
.
/sbin/mstpd.
B7E305E0:1400EFFF00000000043EE2B7CC05E3B7B7E305F0:1400EFFF2F7362696E2F6E7470640000.
.
.
.
/sbin/ntpd.
.
【相关命令】displayprocessmemoryheapdisplayprocessmemoryheapsize1.
1.
12displayprocessmemoryheapsizedisplayprocessmemoryheapsize命令用来显示指定大小已使用内存块的地址.
【命令】displayprocessmemoryheapjobjob-idsizememory-size[offsetoffset-size]【视图】任意视图【缺省用户角色】network-adminnetwork-operator【参数】jobjob-id:任务编号,用于唯一标识一个进程,该编号不会随着进程的重启而改变,取值范围为1~2147483647.
sizememory-size:内存块大小,取值范围为1~4294967295.
offsetoffset-size:要查询的内存块的偏移,取值范围为0~4294967295,缺省值为128.
比如,系统给job1分配了size为16字节的内存块100个,进程当前已用了66个,如果执行命令displayprocessmemoryheapjob1size16offset50,则会显示该进程第51到第66个size为16字节的内存块的地址.
1-22【使用指导】该命令显示的地址为十六进制格式,使用该地址,通过displayprocessmemoryheapaddress命令可以显示该地址内存的具体内容.
【举例】#显示job1已使用的size大小为16字节的内存块的地址.
displayprocessmemoryheapjob1size160xb7e300c00xb7e300d00xb7e300e00xb7e300f00xb7e301000xb7e301100xb7e301200xb7e301300xb7e301400xb7e301500xb7e301600xb7e301700xb7e301800xb7e301900xb7e301a00xb7e301b00xb7e301c00xb7e301d00xb7e301e00xb7e301f00xb7e302000xb7e302100xb7e302200xb7e30230#显示job1已使用的size大小为16字节的内存块的地址,从第5个已使用内存块开始显示.
displayprocessmemoryheapjob1size16offset40xb7e301000xb7e301100xb7e301200xb7e301300xb7e301400xb7e301500xb7e301600xb7e301700xb7e301800xb7e301900xb7e301a00xb7e301b00xb7e301c00xb7e301d00xb7e301e00xb7e301f00xb7e302000xb7e302100xb7e302200xb7e30230【相关命令】displayprocessmemoryheapdisplayprocessmemoryheapaddress1.
1.
13exceptionfilepathexceptionfilepath命令用来设置core文件的保存路径.
undoexceptionfilepath命令用来将core文件的保存路径设置为空.
【命令】exceptionfilepathdirectoryundoexceptionfilepathdirectory【缺省情况】core文件的保存在存储介质的根目录下.
【视图】用户视图【缺省用户角色】network-admin【参数】directory:表示core文件的保存路径,只能为存储介质的根目录.
1-23【使用指导】本命令配置成功后,设备会将生成的core文件存放到当前主用主控板上、指定存储介质根目录下的core文件夹下.
如果存储介质根目录下没有core文件夹,则会先创建core文件夹,再保存core文件.
当主控板上有多块存储介质的时候,可使用该命令修改core文件的保存路径.
需要注意的是,当core文件的保存路径为空或无法正常访问时,系统将无法保存core文件.
【举例】#设置core文件的保存路径.
exceptionfilepathflash:/【相关命令】displayexceptionfilepathprocesscore1.
1.
14monitorkerneldeadloopenablemonitorkerneldeadloopenable命令用来开启内核线程死循环检测功能.
undomonitorkerneldeadloopenable命令用来关闭内核线程死循环检测功能.
【命令】monitorkerneldeadloopenableundomonitorkerneldeadloopenable【缺省情况】内核线程死循环检测功能处于关闭状态.
【视图】系统视图【缺省用户角色】network-admin【使用指导】在内核态空间中,所有资源都是共享的,多个内核线程之间通过任务调度协调工作.
如果某个内核线程长时间一直占用CPU,就会导致其它内核线程获取不到运行机会,整个系统挂死,我们称这种现象为死循环.
开启内核线程死循环检测功能后,如果系统发现某内核线程在指定时间内一直占用CPU,则判定该内核线程为死循环.
系统会记录一条死循环信息供管理员查询,并自动重启整个系统来解除死循环.
开机后,系统会自动检测内核线程是否发生了死循环,建议用户不要随意配置该命令.
如果确实需要配置,请在H3C工程师的指导下进行,以免引起系统异常.
【举例】#开启内核线程死循环检测功能.
system-view[Sysname]monitorkerneldeadloopenable1-24【相关命令】displaykerneldeadloopdisplaykerneldeadloopconfigurationmonitorkerneldeadloopexclude-threadmonitorkerneldeadlooptime1.
1.
15monitorkerneldeadloopexclude-threadmonitorkerneldeadloopexclude-thread命令用来配置不检测指定内核线程是否发生了死循环.
undomonitorkerneldeadloopexclude-thread命令用来恢复对指定内核线程是否发生了死循环进行检测.
【命令】monitorkerneldeadloopexclude-threadtidundomonitorkerneldeadloopexclude-thread[tid]【缺省情况】开启内核线程死循环检测功能后,系统会监控所有内核线程是否发生了死循环.
【视图】系统视图【缺省用户角色】network-admin【参数】tid:表示内核线程编号,用于唯一标识一个内核线程,取值范围为1~2147483647.
不指定该参数时,表示恢复到缺省情况.
【使用指导】缺省情况下,系统会检测所有内核线程是否发生了死循环.
多次执行该命令,可以配置对多个内核线程不进行检测,最多可以配置128个.
开机后,系统会自动检测内核线程是否发生了死循环,建议用户不要随意配置该命令.
如果确实需要配置,请在H3C工程师的指导下进行,以免引起系统异常.
【举例】#对编号为15的内核线程不进行死循环检测.
system-view[Sysname]monitorkerneldeadloopexclude-thread15【相关命令】displaykerneldeadloopconfigurationdisplaykerneldeadloopmonitorkerneldeadloopenablemonitorkerneldeadlooptime1-251.
1.
16monitorkerneldeadlooptimemonitorkerneldeadlooptime命令用来配置判定内核线程是否死循环的时长.
undomonitorkerneldeadlooptime命令用来恢复缺省情况.
【命令】monitorkerneldeadlooptimeintervalundomonitorkerneldeadlooptime【缺省情况】当某内核线程连续运行超过8秒钟,则判定为死循环.
【视图】系统视图【缺省用户角色】network-admin【参数】timeinterval:表示内核线程死循环判定时长,取值范围为1~65535,单位为秒.
【使用指导】开启内核线程检测功能后,如果某内核线程持续运行指定时间,则认为该内核线程已经死循环,系统将记录一条死循环信息并重启.
开机后,系统会自动检测内核线程是否发生了死循环,建议用户不要随意配置该命令.
如果确实需要配置,请在H3C工程师的指导下进行,以免引起系统异常.
【举例】#配置当某内核线程连续运行超过8秒钟,则判定为死循环.
system-view[Sysname]monitorkerneldeadlooptime8【相关命令】displaykerneldeadloopconfigurationdisplaykerneldeadloopmonitorkerneldeadloopenablemonitorkerneldeadloopexclude-thread1.
1.
17monitorprocessmonitorprocess命令用来显示进程的统计信息.
【命令】monitorprocess[dumbtty][iterationnumber]【视图】任意视图1-26【缺省用户角色】network-admin【参数】dumbtty:以哑终端方式显示进程统计信息(即屏幕不支持定时刷新统计信息).
指定该参数时,全部进程的统计信息以CPU使用率降序排列输出到屏幕上;不指定该参数时,统计信息以交互模式显示,缺省情况下按CPU占用率降序显示前10个进程的统计信息,且每隔5秒刷新一次.
iterationnumber:表示进程统计信息的显示次数,取值范围为1~4294967295.
指定dumbtty参数时,number的缺省值为1;不指定dumbtty且不配置number参数时,表示显示次数没有限制,统计信息会每隔5秒刷新一次,一直显示.
【使用指导】不指定dumbtty参数的情况下,统计信息以交互模式显示.
交互模式下,系统会自动计算可显示的进程个数,超过屏幕范围的不显示.
交互模式下,用户可通过输入表1-10中指定的交互命令字来执行相应的操作.
表1-10monitorprocess命令支持的交互命令字描述表命令字功能描述或h帮助信息,显示可用的交互式命令字1各物理CPU状态的显示开关.
比如:(1)输入1,分别显示各物理CPU的参数值(2)再次输入1,显示所有CPU的参数的平均值(3)第三次输入1,又分别显示各物理CPU的参数值(4)如此循环缺省情况下,显示所有CPU的参数的平均值c按CPU占用率降序排列,缺省情况下采用降序排列d设置统计信息的更新时间间隔,取值范围为1~2147483647秒,缺省值为5秒f按进程打开的文件句柄数降序排列k终止一个任务,此命令会影响系统运行,请谨慎使用l刷新屏幕m按进程使用内存大小降序排列n改变显示的进程个数,取值范围为0~2147483647(缺省值为10个,0表示不作限制);超过屏幕范围时,仍只显示一屏内可容纳的进程个数q退出交互模式t按进程最近一次启动后的运行时间降序排列排序项向右移动一列1-27【举例】#以哑终端方式显示进程统计信息.
(使用该方式显示时,系统会一次显示所有进程的统计信息,并且不支持定时刷新,显示完毕后,会退回到命令视图)monitorprocessdumbtty76processes;103threads;687fdsThreadstates:1running,102sleeping,0stopped,0zombieCPUstates:77.
16%idle,0.
00%user,14.
96%kernel,7.
87%interruptMemory:496Mtotal,341Mavailable,pagesize4KJIDPIDPRIStateFDsMEMHH:MM:SSCPUName10471047120R91420K00:02:2313.
53%diagd11120S171092K00:00:207.
61%scmd10001000115S00K00:00:090.
84%[sock/1]10261026120S2026044K00:00:050.
84%syslogd22115S00K00:00:000.
00%[kthreadd]3399S00K00:00:000.
00%[migration/0]44115S00K00:00:060.
00%[ksoftirqd/0]5599S00K00:00:000.
00%[watchdog/0]66115S00K00:00:010.
00%[events/0]77115S00K00:00:000.
00%[khelper]47974797120S828832K00:00:020.
00%comsh51175117120S81496K00:00:000.
00%top#以哑终端方式显示进程统计信息,并且执行一次命令显示两次统计结果.
monitorprocessdumbttyiteration276processes;103threads;687fdsThreadstates:1running,102sleeping,0stopped,0zombieCPUstates:44.
84%idle,0.
51%user,39.
17%kernel,15.
46%interruptMemory:496Mtotal,341Mavailable,pagesize4KJIDPIDPRIStateFDsMEMHH:MM:SSCPUName10471047120R91420K00:02:3037.
11%diagd11120S171092K00:00:2111.
34%scmd10001000115S00K00:00:092.
06%[sock/1]10261026120S2026044K00:00:051.
54%syslogd10271027120S129280K00:01:121.
03%devd44115S00K00:00:060.
51%[ksoftirqd/0]10091009115S00K00:00:080.
51%[karp/1]10101010115S00K00:00:130.
51%[kND/1]53735373120S81496K00:00:000.
51%top22115S00K00:00:000.
00%[kthreadd]3399S00K00:00:000.
00%[migration/0]5599S00K00:00:000.
00%[watchdog/0]66115S00K00:00:010.
00%[events/0]77115S00K00:00:000.
00%[khelper]47964796120S112744K00:00:000.
00%login47974797120S828832K00:00:030.
00%comsh1-28//5秒钟后,系统会自动统计一次,并显示统计信息如下.
(相当于执行了两次monitorprocessdumbtty,两次执行的时间间隔为5秒)76processes;103threads;687fdsThreadstates:1running,102sleeping,0stopped,0zombieCPUstates:78.
71%idle,0.
16%user,14.
86%kernel,6.
25%interruptMemory:496Mtotal,341Mavailable,pagesize4KJIDPIDPRIStateFDsMEMHH:MM:SSCPUName10471047120R91420K00:02:3114.
25%diagd11120S171092K00:00:214.
25%scmd10271027120S129280K00:01:121.
29%devd10001000115S00K00:00:090.
37%[sock/1]53735373120S81500K00:00:000.
37%top66115S00K00:00:010.
18%[events/0]10091009115S00K00:00:080.
18%[karp/1]10101010115S00K00:00:130.
18%[kND/1]47954795120S112372K00:00:010.
18%telnetd22115S00K00:00:000.
00%[kthreadd]3399S00K00:00:000.
00%[migration/0]44115S00K00:00:060.
00%[ksoftirqd/0]5599S00K00:00:000.
00%[watchdog/0]77115S00K00:00:000.
00%[khelper]47964796120S112744K00:00:000.
00%login47974797120S828832K00:00:030.
00%comsh#以交互方式显示进程统计信息.
monitorprocess76processes;103threads;687fdsThreadstates:1running,102sleeping,0stopped,0zombieCPUstates:78.
98%idle,0.
16%user,14.
57%kernel,6.
27%interruptMemory:496Mtotal,341Mavailable,pagesize4KJIDPIDPRIStateFDsMEMHH:MM:SSCPUName10471047120R91420K00:02:3914.
13%diagd11120S171092K00:00:233.
98%scmd10271027120S129280K00:01:131.
44%devd10001000115S00K00:00:090.
36%[sock/1]10091009115S00K00:00:090.
36%[karp/1]44115S00K00:00:060.
18%[ksoftirqd/0]10101010115S00K00:00:130.
18%[kND/1]47954795120S112372K00:00:010.
18%telnetd54915491120S81500K00:00:000.
18%top22115S00K00:00:000.
00%[kthreadd]以上信息会每隔5秒刷新一次.
输入"h"或"",将显示如下帮助信息.
Helpforinteractivecommands:,hShowtheavailableinteractivecommands1ToggleSMPview:'1'single/separatestates1-29cSortbytheCPUfield(default)dSetthedelayintervalbetweenscreenupdatesfSortbynumberofopenfileskKillajoblRefreshthescreenmSortbymemoryusednSetthemaximumnumberofprocessestodisplayqQuittheinteractivedisplaytSortbyruntimeofprocessessincelastrestartMovesortfieldtothenextrightcolumnPressanykeytocontinue输入"d"后,根据出现的提示如果输入"3",则统计信息将会每隔3秒更新一次.
Enterthedelayintervalbetweenupdates(1~2147483647):3输入"n"后,根据出现的提示如果输入"5",则显示的进程数目将会变为5个.
Enterthemaxnumberofprocssestodisplay(0isunlimited):587processes;113threads;735fdsThreadstates:2running,111sleeping,0stopped,0zombieCPUstates:86.
57%idle,0.
83%user,11.
74%kernel,0.
83%interruptMemory:755Mtotal,414Mavailable,pagesize4KJIDPIDPRIStateFDsMEMHH:MM:SSCPUName864864120S2427020K00:00:438.
95%syslogd11731173120R242664K00:00:012.
37%top866866120S1810276K00:00:090.
69%devd11120S161968K00:00:040.
41%scmd881881120S82420K00:00:070.
41%diagd输入"f",统计信息将以打开的文件句柄数降序输出(c、m、t命令字类似).
87processes;113threads;735fdsThreadstates:1running,112sleeping,0stopped,0zombieCPUstates:90.
66%idle,0.
88%user,5.
77%kernel,2.
66%interruptMemory:755Mtotal,414Mavailable,pagesize4KJIDPIDPRIStateFDsMEMHH:MM:SSCPUName862862120S615384K00:00:010.
00%dbmd905905120S352464K00:00:020.
00%ipbased863863120S311956K00:00:000.
00%had884884120S3130600K00:00:000.
00%lsmd889889120S2961592K00:00:000.
00%routed输入"k"后,根据出现的提示如果输入884,将会终止此JID对应的任务"lsmd".
EntertheJIDtokill:88484processes;107threads;683fdsThreadstates:1running,106sleeping,0stopped,0zombieCPUstates:59.
03%idle,1.
92%user,37.
88%kernel,1.
15%interruptMemory:755Mtotal,419Mavailable,pagesize4KJIDPIDPRIStateFDsMEMHH:MM:SSCPUName862862120S565384K00:00:010.
00%dbmd905905120S352464K00:00:020.
00%ipbased863863120S301956K00:00:000.
00%had1-30889889120S2961592K00:00:000.
00%routed11601160120S2823096K00:00:010.
19%sshd输入"q",将退出交互模式.
表1-11monitorprocess命令显示信息描述表字段描述84processes;107threads;683fds系统的进程总数,线程总数,文件句柄总数Threadstates:1running,102sleeping,0stopped,0zombie线程状态:处于running状态的线程数,处于sleeping(包括interruptiblesleep和uninterruptiblesleep)状态的线程数,处于stopped状态的线程数,处于zombie状态的线程数CPUstatesCPU状态:空闲率,占用率,内核态占用率,中断占用率Memory内存状态:总量,可用内存数,page大小,单位为KBJID任务编号(用于唯一标识一个进程,该编号不会随着进程的重启而改变)PID进程编号PRI进程优先级State进程状态,可能的取值为:R:running,运行状态或处于运行队列S:sleeping,可中断睡眠状态T:tracedorstopped,暂停状态D:uninterruptiblesleep,不可中断睡眠状态Z:zombie,僵死状态FDsfiledescriptions,进程打开的文件句柄数MEM进程所使用的内存大小(内核线程该项显示为0)HH:MM:SS进程自最近一次启动以来的运行时间CPU进程CPU使用率Name进程名称(如果进程名称带有"[]"标记,则表示该进程为内核线程)1.
1.
18monitorthreadmonitorthread命令用来显示线程的统计信息.
【命令】monitorthread[dumbtty][iterationnumber]【视图】任意视图【缺省用户角色】network-admin1-31【参数】dumbtty:以哑终端方式显示线程统计信息(即屏幕不支持定时刷新统计信息).
指定该参数时,全部线程的统计信息以CPU使用率降序排列输出到屏幕上.
不指定该参数时,统计信息以交互模式显示,缺省情况下按CPU占用率降序显示前10个线程的统计信息,且每隔5秒更新一次.
iterationnumber:进程统计信息的显示次数,取值范围为1~4294967295.
指定dumbtty参数时number的缺省值为1;不指定dumbtty且不配置number参数时,表示显示次数没有限制,统计信息会一直显示.
【使用指导】不指定dumbtty参数的情况下,统计信息以交互模式显示.
交互模式下,系统会自动计算可显示的线程个数,超过屏幕范围的不作显示.
交互模式下,用户可通过输入表1-12中指定的交互命令字来执行相应的操作.
表1-12monitorthread命令支持的交互命令字描述表命令字功能描述或h帮助信息,显示可用的交互式命令字d设置统计信息的更新时间间隔,缺省值为5秒k终止一个任务(进程),此命令会影响系统运行,请谨慎使用l刷新屏幕n改变显示的线程个数,取值为0~2147483647(缺省值为10个,0表示不作限制);超过屏幕范围时,仍只显示一屏内可容纳的线程个数q退出交互模式排序项向右移动一列【举例】#以哑终端方式显示线程统计信息.
monitorthreaddumbtty84processes;107threadsThreadstates:1running,106sleeping,0stopped,0zombieCPUstates:83.
19%idle,1.
68%user,10.
08%kernel,5.
04%interruptMemory:755Mtotal,417Mavailable,pagesize4KJIDTIDLAST_CPUPRIStateHH:MM:SSMAXCPUName117511750120R00:00:00110.
75%top110120S00:00:0612.
68%scmd8818810120S00:00:0912.
01%diagd7767760120S00:00:0100.
67%[DEVD]8668660120S00:00:1110.
67%devd220115S00:00:0000.
00%[kthreadd]330115S00:00:0100.
00%[ksoftirqd/0]44099S00:00:0010.
00%[watchdog/0]550115S00:00:0000.
00%[events/0]1-32660115S00:00:0000.
00%[khelper]7967960115S00:00:0000.
00%[kip6fs/1]#以交互模式显示线程统计信息.
monitorthread84processes;107threadsThreadstates:1running,106sleeping,0stopped,0zombieCPUstates:94.
43%idle,0.
76%user,3.
64%kernel,1.
15%interruptMemory:755Mtotal,417Mavailable,pagesize4KJIDTIDLAST_CPUPRIStateHH:MM:SSMAXCPUName117611760120R00:00:0113.
42%top8668660120S00:00:1210.
85%devd8818810120S00:00:0910.
64%diagd110120S00:00:0610.
42%scmd116011600120S00:00:0110.
21%sshd220115S00:00:0000.
00%[kthreadd]330115S00:00:0100.
00%[ksoftirqd/0]44099S00:00:0010.
00%[watchdog/0]550115S00:00:0000.
00%[events/0]660115S00:00:0000.
00%[khelper]输入"h"或"",帮助信息显示如下:Helpforinteractivecommands:,hShowtheavailableinteractivecommandscSortbytheCPUfield(default)dSetthedelayintervalbetweenscreenupdateskKillajoblRefreshthescreennSetthemaximumnumberofthreadstodisplayqQuittheinteractivedisplaytSortbyruntimeofthreadssincelastrestartMovesortfieldtothenextrightcolumnPressanykeytocontinue输入"d"后,根据出现的提示如果输入"3",统计信息将会每隔3秒更新一次.
Enterthedelayintervalbetweenscreenupdates(1~2147483647):3输入"n"后,根据出现的提示如果输入"5",显示的线程数目将会变为5个.
Enterthemaxnumberofthreadstodisplay(0meansunlimited):584processes;107threadsThreadstates:1running,106sleeping,0stopped,0zombieCPUstates:93.
26%idle,0.
99%user,4.
23%kernel,1.
49%interruptMemory:755Mtotal,417Mavailable,pagesize4KJIDTIDLAST_CPUPRIStateHH:MM:SSMAXCPUName117611760120R00:00:0213.
71%top110120S00:00:0610.
92%scmd8668660120S00:00:1310.
69%devd8818810120S00:00:1010.
69%diagd1-337207200115D00:00:0100.
23%[TMTH]输入"k"后,根据出现的提示输入881,将会终止此JID对应的任务diagd.
EntertheJIDtokill:88183processes;106threadsThreadstates:1running,105sleeping,0stopped,0zombieCPUstates:96.
26%idle,0.
54%user,2.
63%kernel,0.
54%interruptMemory:755Mtotal,418Mavailable,pagesize4KJIDTIDLAST_CPUPRIStateHH:MM:SSMAXCPUName117611760120R00:00:0411.
86%top8668660120S00:00:1410.
87%devd110120S00:00:0710.
49%scmd73073000S00:00:0410.
12%[DIBC]7627620120S00:00:2210.
12%[MNET]输入"q",将退出交互模式.
表1-13monitorthread命令显示信息描述表显示项内容描述84processes;107threads系统的进程总数,线程总数Threadstates线程状态:处于running状态的线程数,处于sleeping(包括interruptiblesleep和uninterruptiblesleep)状态的线程数,处于stopped状态的线程数,处于zombie状态的线程数CPUstatesCPU状态:空闲率,占用率,内核态占用率,中断占用率Memory内存状态:总量,可用内存数,page大小JID任务编号,用于唯一标识一个进程,该编号不会随着进程的重启而改变TID线程编号LAST_CPU线程最近一次被调度所在的CPU的编号PRI线程优先级State进程状态,可能的取值为:R:running,运行状态或处于运行队列S:sleeping,可中断睡眠状态T:tracedorstopped,暂停状态D:uninterruptiblesleep,不可中断睡眠状态Z:zombie,僵死状态HH:MM:SS线程自最近一次启动以来的运行时间MAX线程单次调度占用CPU的最长时间,以毫秒为单位CPU线程CPU使用率Name线程名称(如果线程名称带有"[]"标记,则表示该线程为内核线程)1-341.
1.
19processcoreprocesscore命令用来开启/关闭进程异常时的生成core文件的功能,以及配置能生成的core文件的最大个数.
【命令】processcore{maxcorevalue|off}{jobjob-id|nameprocess-name}【视图】用户视图【缺省情况】同一进程在首次异常时会生成core文件,后续异常不再生成core文件.
即maxcore的最大数值为1.
【缺省用户角色】network-admin【参数】off:表示关闭进程异常时生成core文件的功能.
maxcorevalue:表示开启进程的core文件生成功能,并配置能生成的core文件的最大个数.
value表示进程能生成的core文件的最大个数,取值范围为1~10,缺省值为1.
nameprocess-name:进程的名称,为1~15个字符的字符串,不区分大小写.
processcore命令的配置对进程下的所有实例有效.
jobjob-id:任务ID,用于唯一标识一个进程,该ID不会随着进程的重启而改变,取值范围为1~2147483647.
【使用指导】开启进程的core文件生成功能,并配置能生成的core文件的最大个数后,进程异常重启一次,就会产生一个core文件并记录进程的异常信息.
如果生成的core文件的数目达到最大值,则不再生成新的core文件.
软件开发和维护人员能够根据core文件的内容来定位异常的原因和异常的位置.
因为生成的core文件会占用系统存储资源,如果用户对某些进程的异常退出不关心,可以关闭这些进程的core文件记录功能.
【举例】#关闭进程routed的core文件生成功能.
processcoreoffnamerouted#开启进程routed的core文件生成功能,并且最多可生成5个core文件.
processcoremaxcore5namerouted【相关命令】displayexceptioncontextexceptionfilepath1.
1.
20resetexceptioncontextresetexceptioncontext命令用来清除进程异常时记录的上下文信息.
1-35【命令】resetexceptioncontext【视图】用户视图【缺省用户角色】network-admin【举例】#清除进程异常记录.
resetexceptioncontext【相关命令】displayexceptioncontext1.
1.
21resetkerneldeadloopresetkerneldeadloop命令用来清除内核线程死循环信息.
【命令】resetkerneldeadloop【视图】用户视图【缺省用户角色】network-admin【举例】#清除内核线程死循环信息.
resetkerneldeadloop【相关命令】displaykerneldeadloop1.
1.
22resetkernelexceptionresetkernelexception命令用来清除内核线程的异常信息.
【命令】resetkernelexception【视图】用户视图【缺省用户角色】network-admin1-36【举例】#清除内核线程的异常信息.
resetkernelexception【相关命令】displaykernelexception
1进程监控和维护命令·1-11.
1.
1displayexceptioncontext1-11.
1.
2displayexceptionfilepath1-51.
1.
3displaykerneldeadloop1-61.
1.
4displaykerneldeadloopconfiguration·1-91.
1.
5displaykernelexception·1-101.
1.
6displayprocess1-131.
1.
7displayprocesscpu·1-151.
1.
8displayprocesslog1-171.
1.
9displayprocessmemory·1-171.
1.
10displayprocessmemoryheap·1-191.
1.
11displayprocessmemoryheapaddress1-201.
1.
12displayprocessmemoryheapsize1-211.
1.
13exceptionfilepath·1-221.
1.
14monitorkerneldeadloopenable1-231.
1.
15monitorkerneldeadloopexclude-thread·1-241.
1.
16monitorkerneldeadlooptime·1-251.
1.
17monitorprocess·1-251.
1.
18monitorthread·1-301.
1.
19processcore1-341.
1.
20resetexceptioncontext1-341.
1.
21resetkerneldeadloop1-351.
1.
22resetkernelexception·1-351-11进程监控和维护1.
1进程监控和维护命令displaymemory、displayprocess、displayprocesscpu、monitorprocess和monitorthread命令既可显示进程的相关信息,又可显示内核线程的相关信息,为简便起见,在这些命令中,统一使用"进程"一词来指代.
1.
1.
1displayexceptioncontextdisplayexceptioncontext命令用来显示进程异常时的上下文信息.
【命令】displayexceptioncontext[countvalue]【视图】任意视图【缺省用户角色】network-admin【参数】countvalue:表示上下文信息的显示个数,取值范围为1~20,缺省值为1.
【使用指导】当进程发生一次异常,系统会生成一个core文件,还会生成一条上下文信息,用于记录异常进程的ID、生成core文件的时间、core文件存放的位置、栈信息和寄存器信息.
一个core文件对应一条上下文信息,最多可记录的上下文信息数和可记录的core文件数目相同.
【举例】#显示在x86体系32位设备上的异常上下文信息.
displayexceptioncontextIndex1of1CrashedPID:120(routed)Crashsignal:SIGBUSCrashtime:TueApr917:14:302013Corefilepath:flash:/core/node0_routed_120_7_20130409-171430_1365527670.
core#00xb7caba4a#10x0804cb79#20xb7cd77c4#30x08049f45Backtracestopped.
Registers'contenteax:0xfffffffcebx:0x00000003ecx:0xbfe244ecedx:0x0000000a1-2esp:0xbfe244b8ebp:0xbfe244c8esi:0xffffffffedi:0xbfe24674eip:0xb7caba4aeflag:0x00000292cs:0x00000073ss:0x0000007bds:0x0000007bes:0x0000007bfs:0x00000000gs:0x00000033#显示在x86体系64位设备上的异常上下文信息.
displayexceptioncontextIndex1of1CrashedPID:121(routed)Crashsignal:SIGBUSCrashtime:SunMar3111:12:212013Corefilepath:flash:/core/node0_routed_121_7_20130331-111221_1364728341.
core#00x00007fae7dbad20c#10x00000000004059fa#20x00007fae7dbd96c0#30x0000000000402b29Backtracestopped.
Registers'contentrax:0xfffffffffffffffcrbx:0x00007fff88a5dd10rcx:0xffffffffffffffffrdx:0x000000000000000arsi:0x00007fff88a5dd10rdi:0x0000000000000003rbp:0x00007fff88a5dcf0rsp:0x00007fff88a5dcf0r8:0x00007fae7ea587e0r9:0x0000000000000079r10:0xffffffffffffffffr11:0x0000000000000246r12:0x0000000000405b18r13:0x00007fff88a5ff7ar14:0x00007fff88a5de30r15:0x0000000000000000rip:0x00007fae7dbad20cflag:0x0000000000000246cs:0x0000000000000033ss:0x000000000000002bds:0x0000000000000000es:0x0000000000000000fs:0x0000000000000000gs:0x0000000000000000fs_base:0x00007fae80a5d6a0gs_base:0x0000000000000000orig_ax:0x00000000000000e8#显示在powerpc体系32位设备上的异常上下文信息.
displayexceptioncontextIndex1of1CrashedPID:133(routed)Crashsignal:SIGBUSCrashtime:WedApr1015:47:492013Corefilepath:flash:/core/node0_routed_133_7_20130410-154749_1365608869.
core#00x184720bc#10x10006b4cBacktracestopped.
Registers'contentgrp00:0x000000ee0x7ffd6ad00x1800f4400x00000004grp04:0x7ffd6af80x0000000a0xffffffff0x184720bcgrp08:0x0002d2000x000000030x000000010x1847209c1-3grp12:0x10006b4c0x100205340xd67441000x00000000grp16:0x000000000xa0203ff00xa028b12c0xa028b13cgrp20:0xa028b1480xa028b1680xa028b1780xa028b190grp24:0xa028b1a80xa028b1b80x000000000x7ffd6c08grp28:0x10006cac0x7ffd6f920x184c1b840x7ffd6ae0nip:0x184720bclr:0x10006b4ccr:0x38000022ctr:0x1847209cmsr:0x0002db00xer:0x00000000ret:0xfffffffcdsisr:0x08000000gr3:0x00000003mq:0x00000000trap:0x00000c00dar:0x1833114c#显示在powerpc体系64位设备上的异常上下文信息.
displayexceptioncontextIndex1of1CrashedPID:172(routed)Crashsignal:SIGBUSCrashtime:SatSep1516:53:162007Corefilepath:cfa0:/core/node1_routed_172_7_20070915-165316_1189875196.
core#00x00000fff803c66b4#10x0000000010009b94#20x00000fff80401814Backtracestopped.
Registers'contentgrp00:0x00000000000000ee0x00000fffffd04840grp02:0x00000fff80425c280x0000000000000004grp04:0x00000fffffd048c00x000000000000000agrp06:0xffffffffffffffff0x00000fff803c66b4grp08:0x000000008002d0000x0000000000000000grp10:0x00000000000000000x0000000000000000grp12:0x00000000000000000x00000fff80a096b0grp14:0x000000007b964c000x000000007b7d0000grp16:0x00000000000000010x000000000000000bgrp18:0x00000000000000310x0000000000a205b8grp20:0x0000000000a206770x0000000000000000grp22:0x000000007bb910140x0000000000000000grp24:0xc0000000005ae1c80x0000000000000000grp26:0xc0000001f00bff200xc0000001f00b0000grp28:0x00000fffffd04a300x000000001001aed8grp30:0x00000fffffd04fae0x00000fffffd04840nip:0x00000fff803c66b4lr:0x0000000010009b94cr:0x0000000058000482ctr:0x00000fff803c66acmsr:0x000000008002d000xer:0x0000000000000000ret:0xfffffffffffffffcdsisr:0x0000000000000000gr3:0x0000000000000003softe:0x0000000000000001trap:0x0000000000000c00dar:0x00000fff8059d14c#显示在mips体系32位设备上的异常上下文信息.
displayexceptioncontext1-4Index1of1CrashedPID:182(routed)Crashsignal:SIGBUSCrashtime:SunJan208:11:382013Corefilepath:flash:/core/node4_routed_182_10_20130102-081138_1293955898.
core#00x2af2faf4#10x00406d8cBacktracestopped.
Registers'contentzero:0x00000000at:0x1000dc00v0:0x00000004v1:0x00000003a0:0x00000003a1:0x7fd267e8a2:0x0000000aa3:0x00000001t0:0x00000000t1:0xcf08fa14t2:0x80230510t3:0xfffffff8t4:0x69766520t5:0x00000000t6:0x63cc6000t7:0x44617461s0:0x7fd26f81s1:0x00401948s2:0x7fd268f8s3:0x803e1db0s4:0x803e1da0s5:0x803e1d88s6:0x803e1d70s7:0x803e1d60t8:0x00000008t9:0x2af2fae0k0:0x00000000k1:0x00000000gp:0x2af9a3a0sp:0x7fd267c0s8:0x7fd267c0ra:0x00406d8csr:0x0000dc13lo:0xef9db265hi:0x0000003fbad:0x2add2010cause:0x00800020pc:0x2af2faf4#显示在mips体系64位设备上的异常上下文信息.
displayexceptioncontextIndex1of1CrashedPID:270(routed)Crashsignal:SIGBUSCrashtime:WedMar2712:39:122013Corefilepath:flash:/core/node16_routed_270_10_20130327-123912_1364387952.
core#00x0000005555a3bcb4#10x0000000120006c1cBacktracestopped.
Registers'contentzero:0x0000000000000000at:0x0000000000000014v0:0x0000000000000004v1:0x0000000000000003a0:0x0000000000000003a1:0x000000ffff899d90a2:0x000000000000000aa3:0x0000000000000001a4:0x0000005555a9b4e0a5:0x0000000000000000a6:0xffffffff8021349ca7:0x20696e206368616et0:0x0000000000000000t1:0xffffffff80105068t2:0xffffffff80213890t3:0x0000000000000008s0:0x0000005555a99c40s1:0x000000ffff89af5fs2:0x0000000120007320s3:0x0000005555a5f470s4:0x000000ffff899f80s5:0xffffffff803cc6c0s6:0xffffffff803cc6a8s7:0xffffffff803cc690t8:0x0000000000000002t9:0x0000005555a3bc98k0:0x0000000000000000k1:0x00000000000000001-5gp:0x0000000120020460sp:0x000000ffff899d70s8:0x000000ffff899d80ra:0x0000000120006c1csr:0x000000000400fff3lo:0xdf3b645a1cac08c9hi:0x000000000000007fbad:0x000000555589ba84cause:0x0000000000800020pc:0x0000005555a3bcb4表1-1displayexceptioncontext命令输出信息描述表字段描述CrashedPID发生异常的进程IDCrashsignal导致异常的信号:SIGABRT:异常终止(abort)SIGBUS:总线错误SIGFPE:浮点异常SIGILL:程序执行了非法指令,导致异常SIGQUIT:终端退出符SIGSEGV:无效存储访问SIGSYS:无效系统调用SIGTRAP:跟踪断点时发生了异常SIGXCPU:超过CPU限制(setrlimit)SIGXFSZ:超过文件长度限制(setrlimit)SIGUNKNOW:未知原因Crashtime异常发生的时间Corefilepathcore文件存放的位置Backtracestopped表示栈信息已经显示完毕Registers'content寄存器的内容【相关命令】resetexceptioncontext1.
1.
2displayexceptionfilepathdisplayexceptionfilepath命令用来显示core文件的保存路径.
【命令】displayexceptionfilepath【视图】任意视图【缺省用户角色】network-admin1-6【举例】#显示主控板上core文件的保存路径.
displayexceptionfilepathTheexceptionfilepathisflash:.
1.
1.
3displaykerneldeadloopdisplaykerneldeadloop命令用来显示内核线程死循环信息.
【命令】displaykerneldeadloopshow-number[offset][verbose]【视图】任意视图【缺省用户角色】network-admin【参数】show-number:需要显示的死循环信息的数目,取值范围为1~20.
offset:需要显示的起始条目距最近条目的偏移,取值范围为0~19,缺省值为0.
verbose:表示显示详细信息.
不指定该参数时,显示概要信息.
【举例】#显示最近一条内核线程死循环的概要信息.
displaykerneldeadloop1Deadlooprecord1Description:BUG:softlockup-CPU#0stuckfor61!
[comsh:16306]Recordedat:2013-05-0111:16:00.
823018Occurredat:2013-05-0111:16:00.
823018Instructionaddress:0x4004158cThread:comsh(TID:16306)Context:threadcontextChassis:0Slot:0CPUID:0Kernelmoduleinfo:modulename(mrpnc)moduleaddress(0xe332a000)modulename(12500)moduleaddress(0xe00bd000)#显示最近一条内核线程死循环的详细信息.
displaykerneldeadloop1verboseDeadlooprecord1Description:BUG:softlockup-CPU#0stuckfor61!
[comsh:16306]Recordedat:2013-05-0111:16:00.
823018Occurredat:2013-05-0111:16:00.
823018Instructionaddress:0x4004158cThread:comsh(TID:16306)Context:threadcontextChassis:01-7Slot:0CPUID:0Kernelmoduleinfo:modulename(mrpnc)moduleaddress(0xe332a000)modulename(12500)moduleaddress(0xe00bd000)Last5threadswitches:migration/0(11:16:00.
823018)-->swapper(11:16:00.
833018)-->kthreadd(11:16:00.
833518)-->swapper(11:16:00.
833550)-->disk(11:16:00.
833560)Registercontent:Reg:r0,Val=0x00000000;Reg:r1,Val=0xe2be5ea0;Reg:r2,Val=0x00000000;Reg:r3,Val=0x77777777;Reg:r4,Val=0x00000000;Reg:r5,Val=0x00001492;Reg:r6,Val=0x00000000;Reg:r7,Val=0x0000ffff;Reg:r8,Val=0x77777777;Reg:r9,Val=0x00000000;Reg:r10,Val=0x00000001;Reg:r11,Val=0x0000002c;Reg:r12,Val=0x057d9484;Reg:r13,Val=0x00000000;Reg:r14,Val=0x00000000;Reg:r15,Val=0x02000000;Reg:r16,Val=0xe2be5f00;Reg:r17,Val=0x00000000;Reg:r18,Val=0x00000000;Reg:r19,Val=0x00000000;Reg:r20,Val=0x024c10f8;Reg:r21,Val=0x057d9244;Reg:r22,Val=0x00002000;Reg:r23,Val=0x0000002c;Reg:r24,Val=0x00000002;Reg:r25,Val=0x24000024;Reg:r26,Val=0x00000000;Reg:r27,Val=0x057d9484;Reg:r28,Val=0x0000002c;Reg:r29,Val=0x00000000;Reg:r30,Val=0x0000002c;Reg:r31,Val=0x00000000;Reg:cr,Val=0x84000028;Reg:nip,Val=0x057d9550;Reg:xer,Val=0x00000000;Reg:lr,Val=0x0186eff0;Reg:ctr,Val=0x682f7344;Reg:msr,Val=0x00784b5c;Reg:trap,Val=0x0000b030;Reg:dar,Val=0x77777777;Reg:dsisr,Val=0x40000000;Reg:result,Val=0x00020300;Dumpstack(total1024bytes,16bytes/line):0xe2be5ea0:02be5ec02400002400000000057d94840xe2be5eb0:000000040000000000000028058d34c40xe2be5ec0:02be60a00186eff000000000000000000xe2be5ed0:020405b40000000000000000000000000xe2be5ee0:000000000000000000000000000000000xe2be5ef0:954773350000000000000000000000000xe2be5f00:a0e164210000000000000000000000000xe2be5f10:00000000000000000000000001e900000xe2be5f20:000000000000000000000000000000000xe2be5f30:000000000000000002be66c002be66d00xe2be5f40:02be61e000000002000000000244b3a40xe2be5f50:02be5f900000000802be5fe0000000080xe2be5f60:02be5f8000ac1b1400000000000000001-80xe2be5f70:05b45f9002be5fe00000003002be5fe00xe2be5f80:02be5fc000ac1bf400000000024500000xe2be5f90:000300000000000002be5fe0000000300xe2be5fa0:02be5fc000ac1b1461f12eae024500000xe2be5fb0:0244b37402be5fd00000003002be5fe00xe2be5fc0:02be60600174fff800000000000008000xe2be5fd0:02be5ff000e8937e02be5ff802be5ffc0xe2be5fe0:00000000000000000000000002be60180xe2be5ff0:02be601000e965980000005800002a4f0xe2be6000:02be6010000000000000000002be60680xe2be6010:02be604000e8c6a000001117000000000xe2be6020:02be6040000000000000000002be60980xe2be6030:02270000000000000000000002be60680xe2be6040:02be6060000000010000b03002be60980xe2be6050:00000004022100000000000001e900000xe2be6060:000000000000000000000000000000000xe2be6070:000000000000000002be66c002be66d00xe2be6080:02be61e0000000020000000002be61700xe2be6090:0000000002210000058d34c4057d9244Calltrace:FunctionAddress=0x8012a4b4FunctionAddress=0x8017989cFunctionAddress=0x80179b30FunctionAddress=0x80127438FunctionAddress=0x8012d734FunctionAddress=0x80100a00FunctionAddress=0xe0071004FunctionAddress=0x8016ce0cFunctionAddress=0x801223a0Instructiondump:41a2fe9c812300ec800200ec7f890000409efe8c80010014540b07b940a2fe804bfffe6c807802907f64db784804ea353880000038a000803863000c表1-2displaykerneldeadloop命令显示信息描述表字段描述Description发生死循环的内核线程的描述信息,包括死循环内核线程所在的CPU的编号、内核线程连续运行的时间、内核线程的名称和编号Recordedat内核线程死循环被记录到主控板上的时间点,精确到微秒Occurredat内核线程发生死循环的时间,精确到微秒Instructionaddress内核线程被检测到发生死循环时对应的指令信息Thread发生死循环的内核线程的名称和编号Context内核线程被检测到发生死循环时所在的上下文环境Slot为固定值0,无特殊意义(集中式设备)1-9字段描述CPUID运行该内核线程的CPU的编号Kernelmoduleinfo内核线程被检测到发生死循环时,系统中已加载的内核模块信息.
包括内核模块名和内核模块加载的内存地址Last5threadswitches内核线程被检测到发生死循环时,记录死循环发生的CPU上、最近五次的内核线程切换轨迹.
包括内核线程的名称和内核线程切换时间点,时间精确到微秒Registercontent内核线程被检测到发生死循环时现场的寄存器信息.
Reg表示寄存器名称,Val表示寄存器中保存的值Dumpstack内核线程被检测到发生死循环时现场的堆栈信息Calltrace内核线程被检测到发生死循环时现场的函数调用栈信息,即每级调用函数的指令地址Instructiondump内核线程被检测到发生死循环时对应的指令码.
非法指令用ffffffff表示Noinformationtodisplay表示系统中没有内核线程死循环记录【相关命令】resetkerneldeadloop1.
1.
4displaykerneldeadloopconfigurationdisplaykerneldeadloopconfiguration命令用来显示内核线程死循环监控参数配置.
【命令】displaykerneldeadloopconfiguration【视图】任意视图【缺省用户角色】network-admin【举例】#显示内核线程死循环监控参数配置.
displaykerneldeadloopconfigurationThreaddeadloopdetection:EnabledDeadlooptimer(inseconds):60Threadsexcludedfrommonitoring:1TID:15Name:co0表1-3displaykerneldeadloopconfiguration命令显示信息描述表字段描述Threaddeadloopdetection:Enabled内核线程死循环检测功能处于开启状态Threaddeadloopdetection:Disabled内核线程死循环检测功能处于关闭状态1-10字段描述Deadlooptimer(inseconds):n内核线程死循环判定周期(单位为秒),即内核线程连续运行时间大于n秒时,则判定为死循环Threadsexcludedfrommonitoring不进行死循环检测的内核线程列表,配置monitorkerneldeadloopexclude-thread命令后才会显示该信息Name不进行死循环检测的内核线程的名称TID不进行死循环检测的内核线程的编号Nothreadisexcludedfrommonitoring对所有内核线程都进行死循环检查1.
1.
5displaykernelexceptiondisplaykernelexception命令用来显示内核线程的异常信息.
【命令】displaykernelexceptionshow-number[offset][verbose]【视图】任意视图【缺省用户角色】network-admin【参数】show-number:需要显示的异常信息的数目,取值范围为1~20.
offset:开始显示的条目距最近条目的偏移,取值范围为0~19,缺省值为0.
verbose:显示详细信息.
不指定该参数时,显示概要信息.
【使用指导】当内核线程在运行过程中发生异常时,系统会自动记录异常信息,以便设备维护人员定位问题.
【举例】#显示最近一条内核线程异常的概要信息.
displaykernelexception1Exceptionrecord1Description:Oops[#0]Recordedat:2013-05-0111:16:00.
823018Occurredat:2013-05-0111:16:00.
823018Instructionaddress:0x4004158cThread:comsh(TID:16306)Context:threadcontextChassis:0Slot:0CPUID:0Kernelmoduleinfo:modulename(mrpnc)moduleaddress(0xe332a000)modulename(disk)moduleaddress(0xe00bd000)1-11#显示最近一条内核线程异常的详细信息.
displaykernelexception1verboseExceptionrecord1Description:Oops[#0]Recordedat:2013-05-0111:16:00.
823018Occurredat:2013-05-0111:16:00.
823018Instructionaddress:0x4004158cThread:comsh(TID:16306)Context:threadcontextChassis:0Slot:0CPUID:0Kernelmoduleinfo:modulename(mrpnc)moduleaddress(0xe332a000)modulename(12500)moduleaddress(0xe00bd000)Last5threadswitches:migration/0(11:16:00.
823018)-->swapper(11:16:00.
833018)-->kthreadd(11:16:00.
833518)-->swapper(11:16:00.
833550)-->disk(11:16:00.
833560)Registercontent:Reg:r0,Val=0x00000000;Reg:r1,Val=0xe2be5ea0;Reg:r2,Val=0x00000000;Reg:r3,Val=0x77777777;Reg:r4,Val=0x00000000;Reg:r5,Val=0x00001492;Reg:r6,Val=0x00000000;Reg:r7,Val=0x0000ffff;Reg:r8,Val=0x77777777;Reg:r9,Val=0x00000000;Reg:r10,Val=0x00000001;Reg:r11,Val=0x0000002c;Reg:r12,Val=0x057d9484;Reg:r13,Val=0x00000000;Reg:r14,Val=0x00000000;Reg:r15,Val=0x02000000;Reg:r16,Val=0xe2be5f00;Reg:r17,Val=0x00000000;Reg:r18,Val=0x00000000;Reg:r19,Val=0x00000000;Reg:r20,Val=0x024c10f8;Reg:r21,Val=0x057d9244;Reg:r22,Val=0x00002000;Reg:r23,Val=0x0000002c;Reg:r24,Val=0x00000002;Reg:r25,Val=0x24000024;Reg:r26,Val=0x00000000;Reg:r27,Val=0x057d9484;Reg:r28,Val=0x0000002c;Reg:r29,Val=0x00000000;Reg:r30,Val=0x0000002c;Reg:r31,Val=0x00000000;Reg:cr,Val=0x84000028;Reg:nip,Val=0x057d9550;Reg:xer,Val=0x00000000;Reg:lr,Val=0x0186eff0;Reg:ctr,Val=0x682f7344;Reg:msr,Val=0x00784b5c;Reg:trap,Val=0x0000b030;Reg:dar,Val=0x77777777;Reg:dsisr,Val=0x40000000;Reg:result,Val=0x00020300;Dumpstack(total1024bytes,16bytes/line):0xe2be5ea0:02be5ec02400002400000000057d94840xe2be5eb0:000000040000000000000028058d34c40xe2be5ec0:02be60a00186eff000000000000000001-120xe2be5ed0:020405b40000000000000000000000000xe2be5ee0:000000000000000000000000000000000xe2be5ef0:954773350000000000000000000000000xe2be5f00:a0e164210000000000000000000000000xe2be5f10:00000000000000000000000001e900000xe2be5f20:000000000000000000000000000000000xe2be5f30:000000000000000002be66c002be66d00xe2be5f40:02be61e000000002000000000244b3a40xe2be5f50:02be5f900000000802be5fe0000000080xe2be5f60:02be5f8000ac1b1400000000000000000xe2be5f70:05b45f9002be5fe00000003002be5fe00xe2be5f80:02be5fc000ac1bf400000000024500000xe2be5f90:000300000000000002be5fe0000000300xe2be5fa0:02be5fc000ac1b1461f12eae024500000xe2be5fb0:0244b37402be5fd00000003002be5fe00xe2be5fc0:02be60600174fff800000000000008000xe2be5fd0:02be5ff000e8937e02be5ff802be5ffc0xe2be5fe0:00000000000000000000000002be60180xe2be5ff0:02be601000e965980000005800002a4f0xe2be6000:02be6010000000000000000002be60680xe2be6010:02be604000e8c6a000001117000000000xe2be6020:02be6040000000000000000002be60980xe2be6030:02270000000000000000000002be60680xe2be6040:02be6060000000010000b03002be60980xe2be6050:00000004022100000000000001e900000xe2be6060:000000000000000000000000000000000xe2be6070:000000000000000002be66c002be66d00xe2be6080:02be61e0000000020000000002be61700xe2be6090:0000000002210000058d34c4057d9244Calltrace:FunctionAddress=0x8012a4b4FunctionAddress=0x8017989cFunctionAddress=0x80179b30FunctionAddress=0x80127438FunctionAddress=0x8012d734FunctionAddress=0x80100a00FunctionAddress=0xe0071004FunctionAddress=0x8016ce0cFunctionAddress=0x801223a0Instructiondump:41a2fe9c812300ec800200ec7f890000409efe8c80010014540b07b940a2fe804bfffe6c807802907f64db784804ea353880000038a000803863000c本命令显示信息的详细描述请参见表1-2.
【相关命令】resetkernelexception1-131.
1.
6displayprocessdisplayprocess命令用来显示进程的状态信息.
【命令】displayprocess[all|jobjob-id|nameprocess-name]【视图】任意视图【缺省用户角色】network-adminnetwork-operator【参数】all:显示所有进程的状态信息.
指定all参数和不指定任何可选参数时,命令行的执行效果相同.
jobjob-id:任务编号,用于唯一标识一个进程,该编号不会随着进程的重启而改变,取值范围为1~2147483647.
nameprocess-name:进程名称,为1~15个字符的字符串,不区分大小写,不能包含问号和空格.
【举例】#显示进程scmd的状态信息.
displayprocessnamescmdJobID:1PID:1ParentJID:0ParentPID:0Executablepath:-Instance:0Respawn:OFFRespawncount:1Max.
spawnsperminute:0Laststarted:WedJun114:45:462013Processstate:sleepingMax.
core:0ARGS:-TIDLAST_CPUStackPRIStateHH:MM:SS:MSECName100K120S0:0:5:220scmd表1-4displayprocessname命令显示信息描述表字段描述JobID任务编号,用于唯一标识一个进程,该编号不会随着进程的重启而改变PID进程编号,用于标识一个进程,但该编号可能会随着进程的重启而改变ParentJID父进程的任务编号ParentPID父进程的进程编号Executablepath进程执行路径(内核线程执行路径显示为"-")1-14字段描述Instance进程的实例号(一个进程根据需要在软件实现时决定了它是否会运行多个实例)Respawn运行出错时,该进程是否会自动重启:ON表示自动重启OFF表示不自动重启Respawncount进程重启的次数(初始值为1)Max.
spawnsperminute进程一分钟内允许异常重启的最大次数(如果进程在一分钟内异常重启次数超过该值,则系统会自动关闭该进程)Laststarted进程最近一次启动的日期和时间Processstate进程状态,可能的取值为:running:运行状态或正在队列中等待调度sleeping:可中断睡眠状态tracedorstopped:暂停状态uninterruptiblesleep:不可中断睡眠状态zombie:僵死状态(僵死状态指的是进程已经退出,但是仍然占用部分资源的状态)Max.
core进程最多可以生成的core文件的数量,如果为0表示不生成core文件(进程异常重启一次,会产生一个core文件.
如果生成的core文件的数目达到最大值,则不再生成core文件.
软件开发和维护人员能够根据core文件的内容来定位异常的原因和异常的位置)ARGS进程启动时携带的参数.
如果进程不带参数,显示为"-"TID线程编号LAST_CPU进程最近一次被调度时,所在的CPUStack堆栈大小PRI线程优先级State线程状态,可能的取值为:R:running,运行状态或正在队列中等待调度S:sleeping,可中断睡眠状态T:tracedorstopped,暂停状态D:uninterruptiblesleep,不可中断睡眠状态Z:zombie,僵死状态HH:MM:SS:MSEC进程最近一次启动后的运行时间Name进程名称#显示所有进程的状态信息.
displayprocessallJIDPID%CPU%MEMSTATPRITTYHH:MM:SSCOMMAND110.
00.
0S120-00:00:04scmd220.
00.
0S115-00:00:00[kthreadd]1-15330.
00.
0S99-00:00:00[migration/0]440.
00.
0S115-00:00:05[ksoftirqd/0]550.
00.
0S99-00:00:00[watchdog/0]660.
00.
0S115-00:00:00[events/0]770.
00.
0S115-00:00:00[khelper]880.
00.
0S115-00:00:00[kblockd/0]990.
00.
0S115-00:00:00[ata/0]10100.
00.
0S115-00:00:00[ata_aux]11110.
00.
0S115-00:00:00[kseriod]12120.
00.
0S120-00:00:00[vzmond]13130.
00.
0S120-00:00:00[pdflush]14140.
00.
0S120-00:00:00[pdflush]15150.
00.
0S115-00:00:00[kswapd0]16160.
00.
0S115-00:00:00[aio/0]17170.
00.
0S115-00:00:00[scsi_eh_0]18180.
00.
0S115-00:00:00[scsi_eh_1]19190.
00.
0S115-00:00:00[scsi_eh_2]35350.
00.
0D100-00:00:00[lipc_topology]----More----表1-5displayprocessall命令显示信息描述字段描述JID任务编号,用于唯一标识一个进程,该编号不会随着进程的重启而改变PID进程编号%CPUCPU使用率(用百分比表示)%MEM内存使用率(用百分比表示)STAT进程状态,可能的取值为:R:running,运行状态或处于运行队列S:sleeping,可中断睡眠状态T:tracedorstopped,暂停状态D:uninterruptiblesleep,不可中断睡眠状态Z:zombie,僵死状态PRI进程优先级(优先级在进程调度时发挥作用,优先级高的会优先得到调度)TTY进程使用的终端HH:MM:SS进程最近一次启动后的运行时间COMMAND进程名称以及进程运行的参数(如果进程名称带有"[]"标记,则表示内核线程)1.
1.
7displayprocesscpudisplayprocesscpu命令用来显示所有进程的CPU使用率信息.
【命令】displayprocesscpu1-16【视图】任意视图【缺省用户角色】network-adminnetwork-operator【举例】#显示所有进程CPU使用率信息.
displayprocesscpuCPUutilizationin5secs:16.
8%;1min:4.
7%;5mins:4.
7%JID5Sec1Min5MinName10.
0%0.
0%0.
0%scmd20.
0%0.
0%0.
0%[kthreadd]30.
1%0.
0%0.
0%[ksoftirqd/0]40.
0%0.
0%0.
0%[watchdog/0]50.
0%0.
0%0.
0%[events/0]60.
0%0.
0%0.
0%[khelper]290.
0%0.
0%0.
0%[kblockd/0]490.
0%0.
0%0.
0%[vzmond]520.
0%0.
0%0.
0%[pdflush]530.
0%0.
0%0.
0%[pdflush]540.
0%0.
0%0.
0%[kswapd0]1100.
0%0.
0%0.
0%[aio/0]7120.
0%0.
0%0.
0%[mtdblockd]7190.
0%0.
0%0.
0%[TNetJob]7200.
0%0.
0%0.
0%[TMTH]7270.
0%0.
0%0.
0%[CF]7300.
0%0.
0%0.
0%[DIBC]7520.
0%0.
0%0.
0%[lipc_topology]7620.
0%0.
0%0.
0%[MNET]7630.
0%0.
0%0.
0%[SYSM]----More----表1-6displayprocesscpu命令显示信息描述表字段描述CPUutilizationin5secs:16.
8%;1min:4.
7%;5mins:4.
7%系统最近5秒CPU使用率;最近1分钟CPU使用率;最近5分钟CPU使用率JID任务编号(用于唯一标识一个进程,该编号不会随着进程的重启而改变)5Sec最近5秒钟内进程的CPU使用率1Min最近1分钟内进程的CPU使用率5Min最近5分钟内进程的CPU使用率Name进程名称(如果进程名称带有"[]"标记,则表示该进程为内核线程)1-171.
1.
8displayprocesslogdisplayprocesslog命令用来显示所有进程的日志信息.
【命令】displayprocesslog【视图】任意视图【缺省用户角色】network-adminnetwork-operator【举例】#显示所有进程的日志信息.
displayprocesslogNameJIDPIDAbortCoreStart-timeEnd-timemdcd135135NN2013-06-1109:31:002013-06-1109:31:00knotify156156NN2013-06-1109:31:022013-06-1109:31:02knotify158158NN2013-06-1109:31:022013-06-1109:31:02knotify195195NN2013-06-1109:31:032013-06-1109:31:03pkg_update203203NN2013-06-1109:31:062013-06-1109:31:06autocfgd219219NN2013-06-1109:31:132013-06-1109:31:13comsh202202NN2013-06-1109:31:052013-06-1109:31:13表1-7displayprocesslog命令显示信息描述表字段描述Name进程名JID进程任务编号PID进程编号Abort是否异常退出:Y表示异常退出N表示正常退出Core是否产生core文件Y表示产生N表示未产生Start-time进程创建时间End-time进程结束时间1.
1.
9displayprocessmemorydisplayprocessmemory命令用来显示所有进程的代码段、数据段以及堆栈等的内存使用信息.
1-18【命令】displayprocessmemory【视图】任意视图【缺省用户角色】network-adminnetwork-operator【使用指导】进程启动时,会向系统申请Text、Data、Stack和Dynamic类型的内存.
Text类型的内存用来存放进程的代码.
Data类型的内存用来存放进程的数据.
Stack内存指的是栈内存,一般存放临时数据.
Dynamic类型的内存指的是堆内存(heap),由系统根据进程运行需要进行动态分配(malloc)和释放(free),可使用displayprocessmemoryheap命令显示Dynamic类型内存的详细信息.
【举例】#显示所有进程的内存使用信息.
displayprocessmemoryJIDTextDataStackDynamicName138418001636scmd20000[kthreadd]30000[ksoftirqd/0]40000[watchdog/0]50000[events/0]60000[khelper]290000[kblockd/0]490000[vzmond]520000[pdflush]----More----表1-8displayprocessmemory命令显示信息描述表字段描述JID任务编号.
用于唯一标识一个进程,该编号不会随着进程的重启而改变Text进程占用的代码段大小,单位为KB(内核线程该项大小为0)Data进程占用的数据段大小,单位为KB(内核线程该项大小为0)Stack进程占用的堆栈大小,单位为KB(内核线程该项大小为0)Dynamic进程动态申请内存大小,单位为KB(内核线程该项大小为0)Name进程名称(如果进程名称带有"[]"标记,则表示该进程为内核线程)1-19【相关命令】displayprocessmemoryheapdisplayprocessmemoryheapaddressdisplayprocessmemoryheapsize1.
1.
10displayprocessmemoryheapdisplayprocessmemoryheap命令用来显示指定进程的堆内存统计信息.
【命令】displayprocessmemoryheapjobjob-id[verbose]【视图】任意视图【缺省用户角色】network-adminnetwork-operator【参数】jobjob-id:任务编号,用于唯一标识一个进程,该编号不会随着进程的重启而改变.
取值范围为1~2147483647.
verbose:显示内存详细统计信息.
不指定该参数时,显示内存概要统计信息.
【使用指导】系统的堆内存由固定大小(比如size=16字节、size=64字节等)的内存块构成,用于存放进程运行过程中需要用到的数据或者中间变量.
当进程启动时,系统会根据进程运行需要,给进程动态分配堆内存.
进程的堆内存信息可使用displayprocessmemoryheap命令显示.
每个内存块都有地址,该地址用十六进制数表示,可通过displayprocessmemoryheapsize命令显示.
用户使用内存块的地址可以访问内存块,获取内存块的内容,内存块的内容可通过displayprocessmemoryheapaddress命令显示.
【举例】#显示job148的堆内存概要统计信息.
displayprocessmemoryheapjob148Totalvirtualmemoryheapspace(inbytes):2228224Totalphysicalmemoryheapspace(inbytes):262144Totalallocatedmemory(inbytes):161576#显示job148的堆内存详细统计信息.
displayprocessmemoryheapjob148verboseHeapusage:SizeFreeUsedTotalFreeRatio168526013%643126212650.
2%12822072091%512355585.
1%409632973001%1-208192119205%819200110%Summary:Totalvirtualmemoryheapspace(inbytes):2293760Totalphysicalmemoryheapspace(inbytes):58368Totalallocatedmemory(inbytes):42368以上显示信息表明:job148分得size大小16字节的内存块60个(已用52个,还有8个未使用),size大小为64字节的内存块1265个(已用1262个,还有3个未使用),以此类推.
表1-9displayprocessmemoryheap命令显示信息描述表命令字功能描述Totalvirtualmemoryheapspace(inbytes)虚拟堆内存总大小,单位为字节Totalphysicalmemoryheapspace(inbytes)物理堆内存总大小,单位为字节Totalallocatedmemory(inbytes)任务已使用的堆内存大小,单位为字节Size内存块大小,单位为字节Free空闲的内存块个数Used已使用的内存块个数Total指定大小内存块总个数,为Free和Used之和FreeRatioFree与Total的比率,可以反映这种大小内存块的碎片情况【相关命令】displayprocessmemorydisplayprocessmemoryheapaddressdisplayprocessmemoryheapsize1.
1.
11displayprocessmemoryheapaddressdisplayprocessmemoryheapaddress命令用来显示从指定地址开始的内存空间的内容.
【命令】displayprocessmemoryheapjobjob-idaddressstarting-addresslengthmemory-length【视图】任意视图【缺省用户角色】network-adminnetwork-operator1-21【参数】jobjob-id:任务编号,用于唯一标识一个进程,该编号不会随着进程的重启而改变,取值范围为1~2147483647.
addressstarting-address:内存块的起始地址.
lengthmemory-length:内存的长度,取值范围为1~1024,单位为字节.
【使用指导】当进程运行异常时,使用该命令可以帮助设备维护人员诊断和定位问题.
【举例】#显示job1从地址0xb7e30580开始,长度为128字节的内存空间的内容.
displayprocessmemoryheapjob1addressb7e30580length128B7E30580:1400EFFF00000000E439E2B77C05E3B79.
.
|.
.
.
B7E30590:1400EFFF2F7362696E2F736C62676400.
.
.
.
/sbin/slbgd.
B7E305A0:1400EFFF00000000443BE2B78C05E3B7.
.
.
.
.
.
.
.
D;.
.
.
.
.
.
B7E305B0:1400EFFF2F7362696E2F6F7370666400.
.
.
.
/sbin/ospfd.
B7E305C0:1400EFFF00000000A43CE2B7AC05E3B7B7E305D0:1400EFFF2F7362696E2F6D7374706400.
.
.
.
/sbin/mstpd.
B7E305E0:1400EFFF00000000043EE2B7CC05E3B7B7E305F0:1400EFFF2F7362696E2F6E7470640000.
.
.
.
/sbin/ntpd.
.
【相关命令】displayprocessmemoryheapdisplayprocessmemoryheapsize1.
1.
12displayprocessmemoryheapsizedisplayprocessmemoryheapsize命令用来显示指定大小已使用内存块的地址.
【命令】displayprocessmemoryheapjobjob-idsizememory-size[offsetoffset-size]【视图】任意视图【缺省用户角色】network-adminnetwork-operator【参数】jobjob-id:任务编号,用于唯一标识一个进程,该编号不会随着进程的重启而改变,取值范围为1~2147483647.
sizememory-size:内存块大小,取值范围为1~4294967295.
offsetoffset-size:要查询的内存块的偏移,取值范围为0~4294967295,缺省值为128.
比如,系统给job1分配了size为16字节的内存块100个,进程当前已用了66个,如果执行命令displayprocessmemoryheapjob1size16offset50,则会显示该进程第51到第66个size为16字节的内存块的地址.
1-22【使用指导】该命令显示的地址为十六进制格式,使用该地址,通过displayprocessmemoryheapaddress命令可以显示该地址内存的具体内容.
【举例】#显示job1已使用的size大小为16字节的内存块的地址.
displayprocessmemoryheapjob1size160xb7e300c00xb7e300d00xb7e300e00xb7e300f00xb7e301000xb7e301100xb7e301200xb7e301300xb7e301400xb7e301500xb7e301600xb7e301700xb7e301800xb7e301900xb7e301a00xb7e301b00xb7e301c00xb7e301d00xb7e301e00xb7e301f00xb7e302000xb7e302100xb7e302200xb7e30230#显示job1已使用的size大小为16字节的内存块的地址,从第5个已使用内存块开始显示.
displayprocessmemoryheapjob1size16offset40xb7e301000xb7e301100xb7e301200xb7e301300xb7e301400xb7e301500xb7e301600xb7e301700xb7e301800xb7e301900xb7e301a00xb7e301b00xb7e301c00xb7e301d00xb7e301e00xb7e301f00xb7e302000xb7e302100xb7e302200xb7e30230【相关命令】displayprocessmemoryheapdisplayprocessmemoryheapaddress1.
1.
13exceptionfilepathexceptionfilepath命令用来设置core文件的保存路径.
undoexceptionfilepath命令用来将core文件的保存路径设置为空.
【命令】exceptionfilepathdirectoryundoexceptionfilepathdirectory【缺省情况】core文件的保存在存储介质的根目录下.
【视图】用户视图【缺省用户角色】network-admin【参数】directory:表示core文件的保存路径,只能为存储介质的根目录.
1-23【使用指导】本命令配置成功后,设备会将生成的core文件存放到当前主用主控板上、指定存储介质根目录下的core文件夹下.
如果存储介质根目录下没有core文件夹,则会先创建core文件夹,再保存core文件.
当主控板上有多块存储介质的时候,可使用该命令修改core文件的保存路径.
需要注意的是,当core文件的保存路径为空或无法正常访问时,系统将无法保存core文件.
【举例】#设置core文件的保存路径.
exceptionfilepathflash:/【相关命令】displayexceptionfilepathprocesscore1.
1.
14monitorkerneldeadloopenablemonitorkerneldeadloopenable命令用来开启内核线程死循环检测功能.
undomonitorkerneldeadloopenable命令用来关闭内核线程死循环检测功能.
【命令】monitorkerneldeadloopenableundomonitorkerneldeadloopenable【缺省情况】内核线程死循环检测功能处于关闭状态.
【视图】系统视图【缺省用户角色】network-admin【使用指导】在内核态空间中,所有资源都是共享的,多个内核线程之间通过任务调度协调工作.
如果某个内核线程长时间一直占用CPU,就会导致其它内核线程获取不到运行机会,整个系统挂死,我们称这种现象为死循环.
开启内核线程死循环检测功能后,如果系统发现某内核线程在指定时间内一直占用CPU,则判定该内核线程为死循环.
系统会记录一条死循环信息供管理员查询,并自动重启整个系统来解除死循环.
开机后,系统会自动检测内核线程是否发生了死循环,建议用户不要随意配置该命令.
如果确实需要配置,请在H3C工程师的指导下进行,以免引起系统异常.
【举例】#开启内核线程死循环检测功能.
system-view[Sysname]monitorkerneldeadloopenable1-24【相关命令】displaykerneldeadloopdisplaykerneldeadloopconfigurationmonitorkerneldeadloopexclude-threadmonitorkerneldeadlooptime1.
1.
15monitorkerneldeadloopexclude-threadmonitorkerneldeadloopexclude-thread命令用来配置不检测指定内核线程是否发生了死循环.
undomonitorkerneldeadloopexclude-thread命令用来恢复对指定内核线程是否发生了死循环进行检测.
【命令】monitorkerneldeadloopexclude-threadtidundomonitorkerneldeadloopexclude-thread[tid]【缺省情况】开启内核线程死循环检测功能后,系统会监控所有内核线程是否发生了死循环.
【视图】系统视图【缺省用户角色】network-admin【参数】tid:表示内核线程编号,用于唯一标识一个内核线程,取值范围为1~2147483647.
不指定该参数时,表示恢复到缺省情况.
【使用指导】缺省情况下,系统会检测所有内核线程是否发生了死循环.
多次执行该命令,可以配置对多个内核线程不进行检测,最多可以配置128个.
开机后,系统会自动检测内核线程是否发生了死循环,建议用户不要随意配置该命令.
如果确实需要配置,请在H3C工程师的指导下进行,以免引起系统异常.
【举例】#对编号为15的内核线程不进行死循环检测.
system-view[Sysname]monitorkerneldeadloopexclude-thread15【相关命令】displaykerneldeadloopconfigurationdisplaykerneldeadloopmonitorkerneldeadloopenablemonitorkerneldeadlooptime1-251.
1.
16monitorkerneldeadlooptimemonitorkerneldeadlooptime命令用来配置判定内核线程是否死循环的时长.
undomonitorkerneldeadlooptime命令用来恢复缺省情况.
【命令】monitorkerneldeadlooptimeintervalundomonitorkerneldeadlooptime【缺省情况】当某内核线程连续运行超过8秒钟,则判定为死循环.
【视图】系统视图【缺省用户角色】network-admin【参数】timeinterval:表示内核线程死循环判定时长,取值范围为1~65535,单位为秒.
【使用指导】开启内核线程检测功能后,如果某内核线程持续运行指定时间,则认为该内核线程已经死循环,系统将记录一条死循环信息并重启.
开机后,系统会自动检测内核线程是否发生了死循环,建议用户不要随意配置该命令.
如果确实需要配置,请在H3C工程师的指导下进行,以免引起系统异常.
【举例】#配置当某内核线程连续运行超过8秒钟,则判定为死循环.
system-view[Sysname]monitorkerneldeadlooptime8【相关命令】displaykerneldeadloopconfigurationdisplaykerneldeadloopmonitorkerneldeadloopenablemonitorkerneldeadloopexclude-thread1.
1.
17monitorprocessmonitorprocess命令用来显示进程的统计信息.
【命令】monitorprocess[dumbtty][iterationnumber]【视图】任意视图1-26【缺省用户角色】network-admin【参数】dumbtty:以哑终端方式显示进程统计信息(即屏幕不支持定时刷新统计信息).
指定该参数时,全部进程的统计信息以CPU使用率降序排列输出到屏幕上;不指定该参数时,统计信息以交互模式显示,缺省情况下按CPU占用率降序显示前10个进程的统计信息,且每隔5秒刷新一次.
iterationnumber:表示进程统计信息的显示次数,取值范围为1~4294967295.
指定dumbtty参数时,number的缺省值为1;不指定dumbtty且不配置number参数时,表示显示次数没有限制,统计信息会每隔5秒刷新一次,一直显示.
【使用指导】不指定dumbtty参数的情况下,统计信息以交互模式显示.
交互模式下,系统会自动计算可显示的进程个数,超过屏幕范围的不显示.
交互模式下,用户可通过输入表1-10中指定的交互命令字来执行相应的操作.
表1-10monitorprocess命令支持的交互命令字描述表命令字功能描述或h帮助信息,显示可用的交互式命令字1各物理CPU状态的显示开关.
比如:(1)输入1,分别显示各物理CPU的参数值(2)再次输入1,显示所有CPU的参数的平均值(3)第三次输入1,又分别显示各物理CPU的参数值(4)如此循环缺省情况下,显示所有CPU的参数的平均值c按CPU占用率降序排列,缺省情况下采用降序排列d设置统计信息的更新时间间隔,取值范围为1~2147483647秒,缺省值为5秒f按进程打开的文件句柄数降序排列k终止一个任务,此命令会影响系统运行,请谨慎使用l刷新屏幕m按进程使用内存大小降序排列n改变显示的进程个数,取值范围为0~2147483647(缺省值为10个,0表示不作限制);超过屏幕范围时,仍只显示一屏内可容纳的进程个数q退出交互模式t按进程最近一次启动后的运行时间降序排列排序项向右移动一列1-27【举例】#以哑终端方式显示进程统计信息.
(使用该方式显示时,系统会一次显示所有进程的统计信息,并且不支持定时刷新,显示完毕后,会退回到命令视图)monitorprocessdumbtty76processes;103threads;687fdsThreadstates:1running,102sleeping,0stopped,0zombieCPUstates:77.
16%idle,0.
00%user,14.
96%kernel,7.
87%interruptMemory:496Mtotal,341Mavailable,pagesize4KJIDPIDPRIStateFDsMEMHH:MM:SSCPUName10471047120R91420K00:02:2313.
53%diagd11120S171092K00:00:207.
61%scmd10001000115S00K00:00:090.
84%[sock/1]10261026120S2026044K00:00:050.
84%syslogd22115S00K00:00:000.
00%[kthreadd]3399S00K00:00:000.
00%[migration/0]44115S00K00:00:060.
00%[ksoftirqd/0]5599S00K00:00:000.
00%[watchdog/0]66115S00K00:00:010.
00%[events/0]77115S00K00:00:000.
00%[khelper]47974797120S828832K00:00:020.
00%comsh51175117120S81496K00:00:000.
00%top#以哑终端方式显示进程统计信息,并且执行一次命令显示两次统计结果.
monitorprocessdumbttyiteration276processes;103threads;687fdsThreadstates:1running,102sleeping,0stopped,0zombieCPUstates:44.
84%idle,0.
51%user,39.
17%kernel,15.
46%interruptMemory:496Mtotal,341Mavailable,pagesize4KJIDPIDPRIStateFDsMEMHH:MM:SSCPUName10471047120R91420K00:02:3037.
11%diagd11120S171092K00:00:2111.
34%scmd10001000115S00K00:00:092.
06%[sock/1]10261026120S2026044K00:00:051.
54%syslogd10271027120S129280K00:01:121.
03%devd44115S00K00:00:060.
51%[ksoftirqd/0]10091009115S00K00:00:080.
51%[karp/1]10101010115S00K00:00:130.
51%[kND/1]53735373120S81496K00:00:000.
51%top22115S00K00:00:000.
00%[kthreadd]3399S00K00:00:000.
00%[migration/0]5599S00K00:00:000.
00%[watchdog/0]66115S00K00:00:010.
00%[events/0]77115S00K00:00:000.
00%[khelper]47964796120S112744K00:00:000.
00%login47974797120S828832K00:00:030.
00%comsh1-28//5秒钟后,系统会自动统计一次,并显示统计信息如下.
(相当于执行了两次monitorprocessdumbtty,两次执行的时间间隔为5秒)76processes;103threads;687fdsThreadstates:1running,102sleeping,0stopped,0zombieCPUstates:78.
71%idle,0.
16%user,14.
86%kernel,6.
25%interruptMemory:496Mtotal,341Mavailable,pagesize4KJIDPIDPRIStateFDsMEMHH:MM:SSCPUName10471047120R91420K00:02:3114.
25%diagd11120S171092K00:00:214.
25%scmd10271027120S129280K00:01:121.
29%devd10001000115S00K00:00:090.
37%[sock/1]53735373120S81500K00:00:000.
37%top66115S00K00:00:010.
18%[events/0]10091009115S00K00:00:080.
18%[karp/1]10101010115S00K00:00:130.
18%[kND/1]47954795120S112372K00:00:010.
18%telnetd22115S00K00:00:000.
00%[kthreadd]3399S00K00:00:000.
00%[migration/0]44115S00K00:00:060.
00%[ksoftirqd/0]5599S00K00:00:000.
00%[watchdog/0]77115S00K00:00:000.
00%[khelper]47964796120S112744K00:00:000.
00%login47974797120S828832K00:00:030.
00%comsh#以交互方式显示进程统计信息.
monitorprocess76processes;103threads;687fdsThreadstates:1running,102sleeping,0stopped,0zombieCPUstates:78.
98%idle,0.
16%user,14.
57%kernel,6.
27%interruptMemory:496Mtotal,341Mavailable,pagesize4KJIDPIDPRIStateFDsMEMHH:MM:SSCPUName10471047120R91420K00:02:3914.
13%diagd11120S171092K00:00:233.
98%scmd10271027120S129280K00:01:131.
44%devd10001000115S00K00:00:090.
36%[sock/1]10091009115S00K00:00:090.
36%[karp/1]44115S00K00:00:060.
18%[ksoftirqd/0]10101010115S00K00:00:130.
18%[kND/1]47954795120S112372K00:00:010.
18%telnetd54915491120S81500K00:00:000.
18%top22115S00K00:00:000.
00%[kthreadd]以上信息会每隔5秒刷新一次.
输入"h"或"",将显示如下帮助信息.
Helpforinteractivecommands:,hShowtheavailableinteractivecommands1ToggleSMPview:'1'single/separatestates1-29cSortbytheCPUfield(default)dSetthedelayintervalbetweenscreenupdatesfSortbynumberofopenfileskKillajoblRefreshthescreenmSortbymemoryusednSetthemaximumnumberofprocessestodisplayqQuittheinteractivedisplaytSortbyruntimeofprocessessincelastrestartMovesortfieldtothenextrightcolumnPressanykeytocontinue输入"d"后,根据出现的提示如果输入"3",则统计信息将会每隔3秒更新一次.
Enterthedelayintervalbetweenupdates(1~2147483647):3输入"n"后,根据出现的提示如果输入"5",则显示的进程数目将会变为5个.
Enterthemaxnumberofprocssestodisplay(0isunlimited):587processes;113threads;735fdsThreadstates:2running,111sleeping,0stopped,0zombieCPUstates:86.
57%idle,0.
83%user,11.
74%kernel,0.
83%interruptMemory:755Mtotal,414Mavailable,pagesize4KJIDPIDPRIStateFDsMEMHH:MM:SSCPUName864864120S2427020K00:00:438.
95%syslogd11731173120R242664K00:00:012.
37%top866866120S1810276K00:00:090.
69%devd11120S161968K00:00:040.
41%scmd881881120S82420K00:00:070.
41%diagd输入"f",统计信息将以打开的文件句柄数降序输出(c、m、t命令字类似).
87processes;113threads;735fdsThreadstates:1running,112sleeping,0stopped,0zombieCPUstates:90.
66%idle,0.
88%user,5.
77%kernel,2.
66%interruptMemory:755Mtotal,414Mavailable,pagesize4KJIDPIDPRIStateFDsMEMHH:MM:SSCPUName862862120S615384K00:00:010.
00%dbmd905905120S352464K00:00:020.
00%ipbased863863120S311956K00:00:000.
00%had884884120S3130600K00:00:000.
00%lsmd889889120S2961592K00:00:000.
00%routed输入"k"后,根据出现的提示如果输入884,将会终止此JID对应的任务"lsmd".
EntertheJIDtokill:88484processes;107threads;683fdsThreadstates:1running,106sleeping,0stopped,0zombieCPUstates:59.
03%idle,1.
92%user,37.
88%kernel,1.
15%interruptMemory:755Mtotal,419Mavailable,pagesize4KJIDPIDPRIStateFDsMEMHH:MM:SSCPUName862862120S565384K00:00:010.
00%dbmd905905120S352464K00:00:020.
00%ipbased863863120S301956K00:00:000.
00%had1-30889889120S2961592K00:00:000.
00%routed11601160120S2823096K00:00:010.
19%sshd输入"q",将退出交互模式.
表1-11monitorprocess命令显示信息描述表字段描述84processes;107threads;683fds系统的进程总数,线程总数,文件句柄总数Threadstates:1running,102sleeping,0stopped,0zombie线程状态:处于running状态的线程数,处于sleeping(包括interruptiblesleep和uninterruptiblesleep)状态的线程数,处于stopped状态的线程数,处于zombie状态的线程数CPUstatesCPU状态:空闲率,占用率,内核态占用率,中断占用率Memory内存状态:总量,可用内存数,page大小,单位为KBJID任务编号(用于唯一标识一个进程,该编号不会随着进程的重启而改变)PID进程编号PRI进程优先级State进程状态,可能的取值为:R:running,运行状态或处于运行队列S:sleeping,可中断睡眠状态T:tracedorstopped,暂停状态D:uninterruptiblesleep,不可中断睡眠状态Z:zombie,僵死状态FDsfiledescriptions,进程打开的文件句柄数MEM进程所使用的内存大小(内核线程该项显示为0)HH:MM:SS进程自最近一次启动以来的运行时间CPU进程CPU使用率Name进程名称(如果进程名称带有"[]"标记,则表示该进程为内核线程)1.
1.
18monitorthreadmonitorthread命令用来显示线程的统计信息.
【命令】monitorthread[dumbtty][iterationnumber]【视图】任意视图【缺省用户角色】network-admin1-31【参数】dumbtty:以哑终端方式显示线程统计信息(即屏幕不支持定时刷新统计信息).
指定该参数时,全部线程的统计信息以CPU使用率降序排列输出到屏幕上.
不指定该参数时,统计信息以交互模式显示,缺省情况下按CPU占用率降序显示前10个线程的统计信息,且每隔5秒更新一次.
iterationnumber:进程统计信息的显示次数,取值范围为1~4294967295.
指定dumbtty参数时number的缺省值为1;不指定dumbtty且不配置number参数时,表示显示次数没有限制,统计信息会一直显示.
【使用指导】不指定dumbtty参数的情况下,统计信息以交互模式显示.
交互模式下,系统会自动计算可显示的线程个数,超过屏幕范围的不作显示.
交互模式下,用户可通过输入表1-12中指定的交互命令字来执行相应的操作.
表1-12monitorthread命令支持的交互命令字描述表命令字功能描述或h帮助信息,显示可用的交互式命令字d设置统计信息的更新时间间隔,缺省值为5秒k终止一个任务(进程),此命令会影响系统运行,请谨慎使用l刷新屏幕n改变显示的线程个数,取值为0~2147483647(缺省值为10个,0表示不作限制);超过屏幕范围时,仍只显示一屏内可容纳的线程个数q退出交互模式排序项向右移动一列【举例】#以哑终端方式显示线程统计信息.
monitorthreaddumbtty84processes;107threadsThreadstates:1running,106sleeping,0stopped,0zombieCPUstates:83.
19%idle,1.
68%user,10.
08%kernel,5.
04%interruptMemory:755Mtotal,417Mavailable,pagesize4KJIDTIDLAST_CPUPRIStateHH:MM:SSMAXCPUName117511750120R00:00:00110.
75%top110120S00:00:0612.
68%scmd8818810120S00:00:0912.
01%diagd7767760120S00:00:0100.
67%[DEVD]8668660120S00:00:1110.
67%devd220115S00:00:0000.
00%[kthreadd]330115S00:00:0100.
00%[ksoftirqd/0]44099S00:00:0010.
00%[watchdog/0]550115S00:00:0000.
00%[events/0]1-32660115S00:00:0000.
00%[khelper]7967960115S00:00:0000.
00%[kip6fs/1]#以交互模式显示线程统计信息.
monitorthread84processes;107threadsThreadstates:1running,106sleeping,0stopped,0zombieCPUstates:94.
43%idle,0.
76%user,3.
64%kernel,1.
15%interruptMemory:755Mtotal,417Mavailable,pagesize4KJIDTIDLAST_CPUPRIStateHH:MM:SSMAXCPUName117611760120R00:00:0113.
42%top8668660120S00:00:1210.
85%devd8818810120S00:00:0910.
64%diagd110120S00:00:0610.
42%scmd116011600120S00:00:0110.
21%sshd220115S00:00:0000.
00%[kthreadd]330115S00:00:0100.
00%[ksoftirqd/0]44099S00:00:0010.
00%[watchdog/0]550115S00:00:0000.
00%[events/0]660115S00:00:0000.
00%[khelper]输入"h"或"",帮助信息显示如下:Helpforinteractivecommands:,hShowtheavailableinteractivecommandscSortbytheCPUfield(default)dSetthedelayintervalbetweenscreenupdateskKillajoblRefreshthescreennSetthemaximumnumberofthreadstodisplayqQuittheinteractivedisplaytSortbyruntimeofthreadssincelastrestartMovesortfieldtothenextrightcolumnPressanykeytocontinue输入"d"后,根据出现的提示如果输入"3",统计信息将会每隔3秒更新一次.
Enterthedelayintervalbetweenscreenupdates(1~2147483647):3输入"n"后,根据出现的提示如果输入"5",显示的线程数目将会变为5个.
Enterthemaxnumberofthreadstodisplay(0meansunlimited):584processes;107threadsThreadstates:1running,106sleeping,0stopped,0zombieCPUstates:93.
26%idle,0.
99%user,4.
23%kernel,1.
49%interruptMemory:755Mtotal,417Mavailable,pagesize4KJIDTIDLAST_CPUPRIStateHH:MM:SSMAXCPUName117611760120R00:00:0213.
71%top110120S00:00:0610.
92%scmd8668660120S00:00:1310.
69%devd8818810120S00:00:1010.
69%diagd1-337207200115D00:00:0100.
23%[TMTH]输入"k"后,根据出现的提示输入881,将会终止此JID对应的任务diagd.
EntertheJIDtokill:88183processes;106threadsThreadstates:1running,105sleeping,0stopped,0zombieCPUstates:96.
26%idle,0.
54%user,2.
63%kernel,0.
54%interruptMemory:755Mtotal,418Mavailable,pagesize4KJIDTIDLAST_CPUPRIStateHH:MM:SSMAXCPUName117611760120R00:00:0411.
86%top8668660120S00:00:1410.
87%devd110120S00:00:0710.
49%scmd73073000S00:00:0410.
12%[DIBC]7627620120S00:00:2210.
12%[MNET]输入"q",将退出交互模式.
表1-13monitorthread命令显示信息描述表显示项内容描述84processes;107threads系统的进程总数,线程总数Threadstates线程状态:处于running状态的线程数,处于sleeping(包括interruptiblesleep和uninterruptiblesleep)状态的线程数,处于stopped状态的线程数,处于zombie状态的线程数CPUstatesCPU状态:空闲率,占用率,内核态占用率,中断占用率Memory内存状态:总量,可用内存数,page大小JID任务编号,用于唯一标识一个进程,该编号不会随着进程的重启而改变TID线程编号LAST_CPU线程最近一次被调度所在的CPU的编号PRI线程优先级State进程状态,可能的取值为:R:running,运行状态或处于运行队列S:sleeping,可中断睡眠状态T:tracedorstopped,暂停状态D:uninterruptiblesleep,不可中断睡眠状态Z:zombie,僵死状态HH:MM:SS线程自最近一次启动以来的运行时间MAX线程单次调度占用CPU的最长时间,以毫秒为单位CPU线程CPU使用率Name线程名称(如果线程名称带有"[]"标记,则表示该线程为内核线程)1-341.
1.
19processcoreprocesscore命令用来开启/关闭进程异常时的生成core文件的功能,以及配置能生成的core文件的最大个数.
【命令】processcore{maxcorevalue|off}{jobjob-id|nameprocess-name}【视图】用户视图【缺省情况】同一进程在首次异常时会生成core文件,后续异常不再生成core文件.
即maxcore的最大数值为1.
【缺省用户角色】network-admin【参数】off:表示关闭进程异常时生成core文件的功能.
maxcorevalue:表示开启进程的core文件生成功能,并配置能生成的core文件的最大个数.
value表示进程能生成的core文件的最大个数,取值范围为1~10,缺省值为1.
nameprocess-name:进程的名称,为1~15个字符的字符串,不区分大小写.
processcore命令的配置对进程下的所有实例有效.
jobjob-id:任务ID,用于唯一标识一个进程,该ID不会随着进程的重启而改变,取值范围为1~2147483647.
【使用指导】开启进程的core文件生成功能,并配置能生成的core文件的最大个数后,进程异常重启一次,就会产生一个core文件并记录进程的异常信息.
如果生成的core文件的数目达到最大值,则不再生成新的core文件.
软件开发和维护人员能够根据core文件的内容来定位异常的原因和异常的位置.
因为生成的core文件会占用系统存储资源,如果用户对某些进程的异常退出不关心,可以关闭这些进程的core文件记录功能.
【举例】#关闭进程routed的core文件生成功能.
processcoreoffnamerouted#开启进程routed的core文件生成功能,并且最多可生成5个core文件.
processcoremaxcore5namerouted【相关命令】displayexceptioncontextexceptionfilepath1.
1.
20resetexceptioncontextresetexceptioncontext命令用来清除进程异常时记录的上下文信息.
1-35【命令】resetexceptioncontext【视图】用户视图【缺省用户角色】network-admin【举例】#清除进程异常记录.
resetexceptioncontext【相关命令】displayexceptioncontext1.
1.
21resetkerneldeadloopresetkerneldeadloop命令用来清除内核线程死循环信息.
【命令】resetkerneldeadloop【视图】用户视图【缺省用户角色】network-admin【举例】#清除内核线程死循环信息.
resetkerneldeadloop【相关命令】displaykerneldeadloop1.
1.
22resetkernelexceptionresetkernelexception命令用来清除内核线程的异常信息.
【命令】resetkernelexception【视图】用户视图【缺省用户角色】network-admin1-36【举例】#清除内核线程的异常信息.
resetkernelexception【相关命令】displaykernelexception
HostYun 新增美国三网CN2 GIA VPS主机 采用美国原生IP低至月15元
在之前几个月中也有陆续提到两次HostYun主机商，这个商家前身是我们可能有些网友熟悉的主机分享团队的，后来改名称的。目前这个品牌主营低价便宜VPS主机，这次有可以看到推出廉价版本的美国CN2 GIA VPS主机，月费地址15元，适合有需要入门级且需要便宜的用户。第一、廉价版美国CN2 GIA VPS主机方案我们可看到这个类型的VPS目前三网都走CN2 GIA网络，而且是原生IP。根据信息可能后续...
百纵科技(19元/月),美国洛杉矶10G防御服务器/洛杉矶C3机房 带金盾高防
百纵科技官网：https://www.baizon.cn/百纵科技:美国云服务器活动重磅来袭,洛杉矶C3机房 带金盾高防,会员后台可自助管理防火墙,添加黑白名单 CC策略开启低中高.CPU全系列E52680v3 DDR4内存 三星固态盘列阵。另有高防清洗！美国洛杉矶 CN2 云服务器CPU内存带宽数据盘防御价格1H1G10M10G10G19元/月 购买地址2H1G10M10G10G29元/月 购买...
弘速云20.8元/月 ，香港云服务器 2核 1g 10M
弘速云元旦活动本公司所销售的弹性云服务器、虚拟专用服务器（VPS）、虚拟主机等涉及网站接入服务的云产品由具备相关资质的第三方合作服务商提供官方网站：https://www.hosuyun.com公司名：弘速科技有限公司香港沙田直营机房采用CTGNET高速回国线路弹性款8折起优惠码:hosu1-1 测试ip:69.165.77.50地区CPU内存硬盘带宽价格购买地址香港沙田2-8核1-16G20-...
系统空闲进程为你推荐
-
openeuleropen与close的区别及用法陈嘉垣反黑阿欣是谁演的 扮演者介绍www.se222se.com原来的www站到底222eee怎么了莫非不是不能222eee在收视com了，/?求解se9999se.comexol.smtown.comlcoc.top日本Ni-TOP是什么意思？www.henhenlu.com有一个两位数，十位数字是个位数字的二分之一，将十位数字与个位数字对调，新的两位数比原来大36，这个两位数www.ijinshan.com金山毒霸的网站是多少33tutu.com33gan.com改成什么了www.toutoulu.comSEO行业外链怎么做？www.dm8.cc有谁知道海贼王最新漫画网址是多少？？