Sponsored Content
Top Forums UNIX for Dummies Questions & Answers How do I determine # of processors ... Post 30075 by auswipe on Wednesday 16th of October 2002 12:01:55 PM
Old 10-16-2002
You should be able to sort the the dmesg output and see all that of information.

run `dmesg | less` to scroll through the dmesg output.
 

10 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

Dual processors

I have two sparcstation20's. One has no hard drive or memory and I want to know if there is a way to take the processor out of it and make the other a dual processor. I know it is possible some how just curious if anyone here can help me make this happen. (Don't know much about sun... (3 Replies)
Discussion started by: jwbrown
3 Replies

2. UNIX for Dummies Questions & Answers

Processors that support Unix

Hello all! My boss wants we to learn a little bit of Unix in the next couple of months so I can broaden my opportunities. What processors will Unix run on? Intel... AMD32.... AMD64... Help Please. I need to build a computer that can support Unix to begin learning. Thanks (3 Replies)
Discussion started by: hkypro7
3 Replies

3. Windows & DOS: Issues & Discussions

Quad or Duel Processors

Which hardware configuration gives you the best though put for processing? 1.) Quad CPU at 2 GHZ 2.) Dual CPU at 3 GHZ and More Memory. We currently have setup #1, I want to upgrade the server and I am investigating hardware configurations. Wanted to know if set #1 gives better though put... (4 Replies)
Discussion started by: rfmurphy_6
4 Replies

4. HP-UX

How do I detect multicore processors?

I'm fairly new to HP-UX, and I need to know how to identify the number of cores on a PA-8800 processor from the command line. Any help here would be appreciated. (11 Replies)
Discussion started by: Midcain
11 Replies

5. UNIX for Dummies Questions & Answers

How do i kill -9 multiple processors at once

Hi There How do i kill multiple processors on unix version 5.05, I know how to kill a single processors individually (e.g kill -9 process number),but i need to do it daily as some users dont log off the systems and keeps processor's running, and when the night jobstream executes it falls over... (7 Replies)
Discussion started by: esh
7 Replies

6. UNIX for Dummies Questions & Answers

check memory and processors

HI , I have AIX 5.2 ? I believe. I am looking to see how many processors I have and what the Memory is in this box? I know there is a command to run but I am really rusty at this Thanks Dave (2 Replies)
Discussion started by: rocker40
2 Replies

7. UNIX for Advanced & Expert Users

No: of processors

which unix command can be used to know the no: of processors running on that machine... version used:- Solaris 8.0 (3 Replies)
Discussion started by: bishweshwar
3 Replies

8. AIX

Need help understand Virtual Processors

First of all I have performed a Google search and internal search and found several descriptions but nothing I can wrap my head around and feel 100% confident about. I feel really silly for asking this as I manage a P6 570 with 12 lpars but I have difficulity with Virtual Processors. I can... (3 Replies)
Discussion started by: juredd1
3 Replies

9. UNIX for Advanced & Expert Users

How to find locked processors

Hi all, i have no of processors .in that some processors locked. how to find the particular locked processors into list of all the processors. i hav no of processors like ex: processors 1021 1022 1023 1024 1025 ---it is locked 1026 -- - - - - -- 2334334 so i don't know 1025 is... (1 Reply)
Discussion started by: venkatreddy
1 Replies

10. Hardware

sun x4100 M2 processors

hi please how to know that a sun x4100 m2 server has one or two processors installed ?? the OS installed on this server is windows 2003 Enterprise Edition. thanks (2 Replies)
Discussion started by: bahjatm
2 Replies
DMESG(1)							   User Commands							  DMESG(1)

NAME
dmesg - print or control the kernel ring buffer SYNOPSIS
dmesg [options] dmesg --clear dmesg --read-clear [options] dmesg --console-level level dmesg --console-on dmesg --console-off DESCRIPTION
dmesg is used to examine or control the kernel ring buffer. The default action is to display all messages from the kernel ring buffer. OPTIONS
The --clear, --read-clear, --console-on, --console-off, and --console-level options are mutually exclusive. -C, --clear Clear the ring buffer. -c, --read-clear Clear the ring buffer after first printing its contents. -D, --console-off Disable the printing of messages to the console. -d, --show-delta Display the timestamp and the time delta spent between messages. If used together with --notime then only the time delta without the timestamp is printed. -E, --console-on Enable printing messages to the console. -e, --reltime Display the local time and the delta in human-readable format. Be aware that conversion to the local time could be inaccurate (see -T for more details). -F, --file file Read the syslog messages from the given file. Note that -F does not support messages in kmsg format. The old syslog format is sup- ported only. -f, --facility list Restrict output to the given (comma-separated) list of facilities. For example: dmesg --facility=daemon will print messages from system daemons only. For all supported facilities see the --help output. -H, --human Enable human-readable output. See also --color, --reltime and --nopager. -k, --kernel Print kernel messages. -L, --color[=when] Colorize the output. The optional argument when can be auto, never or always. If the when argument is omitted, it defaults to auto. The colors can be disabled; for the current built-in default see the --help output. See also the COLORS section below. -l, --level list Restrict output to the given (comma-separated) list of levels. For example: dmesg --level=err,warn will print error and warning messages only. For all supported levels see the --help output. -n, --console-level level Set the level at which printing of messages is done to the console. The level is a level number or abbreviation of the level name. For all supported levels see the --help output. For example, -n 1 or -n alert prevents all messages, except emergency (panic) messages, from appearing on the console. All levels of messages are still written to /proc/kmsg, so syslogd(8) can still be used to control exactly where kernel messages appear. When the -n option is used, dmesg will not print or clear the kernel ring buffer. -P, --nopager Do not pipe output into a pager. A pager is enabled by default for --human output. -r, --raw Print the raw message buffer, i.e. do not strip the log-level prefixes. Note that the real raw format depends on the method how dmesg(1) reads kernel messages. The /dev/kmsg device uses a different for- mat than syslog(2). For backward compatibility, dmesg(1) returns data always in the syslog(2) format. It is possible to read the real raw data from /dev/kmsg by, for example, the command 'dd if=/dev/kmsg iflag=nonblock'. -S, --syslog Force dmesg to use the syslog(2) kernel interface to read kernel messages. The default is to use /dev/kmsg rather than syslog(2) since kernel 3.5.0. -s, --buffer-size size Use a buffer of size to query the kernel ring buffer. This is 16392 by default. (The default kernel syslog buffer size was 4096 at first, 8192 since 1.3.54, 16384 since 2.1.113.) If you have set the kernel buffer to be larger than the default, then this option can be used to view the entire buffer. -T, --ctime Print human-readable timestamps. Be aware that the timestamp could be inaccurate! The time source used for the logs is not updated after system SUSPEND/RESUME. -t, --notime Do not print kernel's timestamps. --time-format format Print timestamps using the given format, which can be ctime, reltime, delta or iso. The first three formats are aliases of the time-format-specific options. The iso format is a dmesg implementation of the ISO-8601 timestamp format. The purpose of this for- mat is to make the comparing of timestamps between two systems, and any other parsing, easy. The definition of the iso timestamp is: YYYY-MM-DD<T>HH:MM:SS,<microseconds><-+><timezone offset from UTC>. The iso format has the same issue as ctime: the time may be inaccurate when a system is suspended and resumed. -u, --userspace Print userspace messages. -w, --follow Wait for new messages. This feature is supported only on systems with a readable /dev/kmsg (since kernel 3.5.0). -x, --decode Decode facility and level (priority) numbers to human-readable prefixes. -V, --version Display version information and exit. -h, --help Display help text and exit. COLORS
Implicit coloring can be disabled by an empty file /etc/terminal-colors.d/dmesg.disable. See terminal-colors.d(5) for more details about colorization configuration. The logical color names supported by dmesg are: subsys The message sub-system prefix (e.g. "ACPI:"). time The message timestamp. timebreak The message timestamp in short ctime format in --reltime or --human output. alert The text of the message with the alert log priority. crit The text of the message with the critical log priority. err The text of the message with the error log priority. warn The text of the message with the warning log priority. segfault The text of the message that inform about segmentation fault. SEE ALSO
terminal-colors.d(5), syslogd(8) AUTHORS
Karel Zak <kzak@redhat.com> dmesg was originally written by Theodore Ts'o <tytso@athena.mit.edu> AVAILABILITY
The dmesg command is part of the util-linux package and is available from Linux Kernel Archive <https://www.kernel.org/pub/linux/utils /util-linux/>. util-linux July 2012 DMESG(1)
All times are GMT -4. The time now is 01:39 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy