There are even more command line utilities available, but they’re not installed by default on some distros, and all the information we need can usually be obtained from the two utilities covered above. The lscpu command also gives us information about our hypervisor and various cache sizes.
Threads per core: 2 (2 threads x 2 cores = 4 logical CPUs).Cores per socket: 2 (therefore we have 2 cores total).Sockets: 1 (this is the actual number of physical CPUs).In particular, we get a nicer breakdown of CPU cores. This tells us a lot of the same information, but some of it’s easier to interpret. Model name: Intel(R) Core(TM) i5-5300U CPU 2.30GHz Enabled flags for the CPU – tells us what features the CPU is capable ofĪnother useful utility, which you may find a bit easier to use because of its concise output, is the lscpu command.Īddress sizes: 39 bits physical, 48 bits virtual.CPU make and model: Intel(R) Core(TM) i5-5300U.Some helpful information from the /proc/cpuinfo virtual file is as follows: Therefore, the procinfo method could output the same information 16 times (assuming you have an 8 core CPU with multithreading). Most CPUs these days have multiple cores, and the operating system will perceive each one as an individual processor. The only downside to this method is that it will output information for each logical processor, so the terminal can get a bit spammy – you could always pipe to more to clean it up. Model name : Intel(R) Core(TM) i5-5300U CPU 2.30GHzįlags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush mmx fxsr sse sse2 ss ht syscall nx pdpe1gb rdtscp lm constant_tsc rep_good nopl xtopology cpuid pni pclmulqdq ssse3 fma cx16 pcid sse4_1 sse4_2 movbe popcnt aes xsave avx f16c rdrand hypervisor lahf_lm abm 3dnowprefetch invpcid_single pti ssbd ibrs ibpb stibp fsgsbase bmi1 hle avx2 smep bmi2 erms invpcid rtm rdseed adx smap xsaveopt flush_l1d arch_capabilitiesīugs : cpu_meltdown spectre_v1 spectre_v2 spec_store_bypass l1tf mds swapgs taa itlb_multihit srbdsĪddress sizes : 39 bits physical, 48 bits virtual The /proc/cpuinfo virtual file contains a lot of information about the CPUs installed in our system. The following methods show the most useful tools, which are installed by default on almost any Linux distribution. # Fix the script to work with wireless/DSL connections.There are several command line utilities we can use to obtain CPU information on Linux. # Make the script more user-friendly in other ways. # Improve the script so it exits on a "q" keystroke. # As it stands, this script must be terminated with a Control-C. Netstat -s | grep "packets received" # Get some connect statistics. # While process running, then "status" file exists. While # Endless loop, script can be improved here. If # If no pid, then process is not running. #+ When a command sequence gets too complex, look for a shortcut. #+ this could have been considerably simplified by using "pidof". # Have to filter out the process lines generated by the search itself. # Finding the process number of 'pppd', the 'ppp daemon'. Pidno=$( ps ax | grep -v "ps ax" | grep -v grep | grep $PROCNAME | # Note that this script may need modification # Additional commentary by Stephane Chazelas.Įxample 29-4. # lsof -aFn -p $1 -d txt | sed -ne 's/^n//p' # However, either of the following would work. #+ because the fifth field of 'ps' is argv of the process, # This elaborate script can *almost* be replaced by
Then #+ then the corresponding process exists. #+ to the complete path name of the invoking process. # /proc/pid-number/exe is a symbolic link Shell scripts may extract data from certain of the files inįS=iso # ISO filesystem support in kernel? OEM info: Panasonic bash$ fgrep Mem /proc/meminfo MemTotal: 515216 kB
0 kommentar(er)
