02-13-2014
Thanks a lot bakunin!
The doubt I have is in the results of the commands output.
For Instance,
Let's take the "User%" from the output of the topas command and compare it with
"us" in the vmstat command
It is 3.1 and 0 respectively. They are not matching though they gauge the same.
In the same way all the values such as Kern%,Wait%,Idle%,Physc and Entc from topas and sy,wa,id,pc &ec are not matching.
Infact the sample output's given were captured one after the other in the same server but the results seems to be not matching.
10 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
Hi,
Is there a command I can use to find out how many CPU's and what type are on my server? (I was told to use cat /proc/cpuinfo)
Also, how do I know what kind of bus speeds are on my server?
Thanks in advance:) (3 Replies)
Discussion started by: ihot
3 Replies
2. HP-UX
is there a single command or location from which one can get information like cpu Mhz,cpu cache...etc in HP UX:) (1 Reply)
Discussion started by: vijayca
1 Replies
3. UNIX for Dummies Questions & Answers
hi, everybody
i have a problem about performane in unix
when i run topas, there 1 form show, there are many parameter about memory,cpu,....
i want to know detail about those
example :
MEMORY
Real,MB 12287
% Comp 25.0
% Noncomp 75.8
% Client 0.5
comp mean ? 25 mean ? 25MB or 25%memory... (6 Replies)
Discussion started by: tokienlua
6 Replies
4. HP-UX
Hi,
I am going to buy a software that is licenced per CORE.
I have a HPUX B1123 64 bit with 8 cpus.
How can i know how many cores are in my machine ?
Thanks (3 Replies)
Discussion started by: yoavbe
3 Replies
5. Shell Programming and Scripting
Dear all,
Is there any generic command working on all Unix listing the CPU of a server?
I found different command line per OS but I am looking for a more generic one.
Thanks for your answer. (5 Replies)
Discussion started by: sgoiffon
5 Replies
6. UNIX for Dummies Questions & Answers
I used the TOPAS command to get top 20 process information by routing the output to a file. But the output is not very readable. can ayone explain how to read the output, or how to interpret the information?
Thanks! (3 Replies)
Discussion started by: ginnyr1
3 Replies
7. AIX
I have a number of LPARs on one P520. All LPARs are running 5.3 and I observe the following:
On some LPARs the number of CPUs found do not match between topas and mpstat.
Server 1:
$ mpstat
System configuration: lcpu=4 ent=0.2 mode=Uncapped
cpu min maj mpc int cs ics rq ... (1 Reply)
Discussion started by: petervg
1 Replies
8. Shell Programming and Scripting
How do i display only one iteration of topas command. Ideally i would topas -P to show only one instance rather than keep on running. is there any swicth? (1 Reply)
Discussion started by: NarayanaPrakash
1 Replies
9. AIX
Hi,
how to grep data from topas command...for example i have to grep owner from topas command
Thanks (2 Replies)
Discussion started by: sumanthupar
2 Replies
10. AIX
seeing weirdness across some 7.1.5.1 LPARs - they all have 2 vCPUs allocated shared. With prtconf they show 2 CPUs, 'lsdev -c processor' concurs, and 'lsattr -El procX' shows that SMT is enabled and there are 2 SMT threads (power5, sorry). Yet running topas on them shows 2 CPUs on some and 4 on... (3 Replies)
Discussion started by: maraixadm
3 Replies
LEARN ABOUT CENTOS
systemd-coredumpctl
SYSTEMD-COREDUMPCTL(1) systemd-coredumpctl SYSTEMD-COREDUMPCTL(1)
NAME
systemd-coredumpctl - Retrieve coredumps from the journal
SYNOPSIS
systemd-coredumpctl [OPTIONS...] {COMMAND} [PID|COMM|EXE|MATCH...]
DESCRIPTION
systemd-coredumpctl may be used to retrieve coredumps from systemd-journald(8).
OPTIONS
The following options are understood:
-h, --help
Print a short help text and exit.
--version
Print a short version string and exit.
-F, --field=
Print all possible data values the specified field takes in matching coredump entries of the journal.
-o, --output=FILE
Write the core to FILE.
--no-pager
Do not pipe output of list into a pager.
--no-legend
Do not print the column headers.
The following commands are understood:
list
List coredumps captured in the journal matching specified characteristics.
dump
Extract the last coredump matching specified characteristics. Coredump will be written on stdout, unless an output file is specified
with -o/--output.
gdb
Invoke the GNU debugger on the last coredump matching specified characteristics.
MATCHING
Match can be:
PID
Process ID of the process that dumped core. An integer.
COMM
Name of the executable (matches COREDUMP_COMM=). Must not contain slashes.
EXE
Path to the executable (matches COREDUMP_EXE=). Must contain at least one slash.
MATCH
General journalctl predicates (see journalctl(1)). Must contain an equals sign.
EXIT STATUS
On success, 0 is returned, a non-zero failure code otherwise. Not finding any matching coredumps is treated as failure.
SEE ALSO
systemd-journald.service(8), gdb(1)
systemd 208 SYSTEMD-COREDUMPCTL(1)