Hello Friends,
On one of my Solaris 10 box, CPU usage shows 100% using "sar", "vmstat". However, it has 4 CPUs and prstat and glance are not showing enough processes to justify high CPU utilization.
=========================================================================
$ prstat -a
... (4 Replies)
I wrote a very simple script that matches combinations of alphabetic characters (1-5). I want to use it to test CPU speeds of different hardware/platforms. The problem is that on multi-core/processor systems, only one CPU is being utilized to execute the script. Is there a way to change that?... (16 Replies)
Hey all,
dmidecode | grep -i CPU
Socket Designation: CPU 0
Version: Intel(R) Xeon(R) CPU E5530 @ 2.40GHz
Socket Designation: CPU 1
Version: Intel(R) Xeon(R) CPU E5530 @ 2.40GHz
cat /proc/cpuinfo | grep -i cpu
cpu family : 6... (24 Replies)
Hi folks,
I want to know how to run two unix programs on two different cpu cores on a 2-core or 4-core or 8-core CPU machine? Extending this how would i run four and eight unix programs on 4-core and 8-core machine respectively?
If this can be done, how to know which program is assigned to... (1 Reply)
Hi Gurus
Can someone help me in explaining the below outputs .
psrinfo -p
4
/usr/sbin/psrinfo -pv
The physical processor has 4 virtual processors (0-3)
SPARC64-VI (portid 1024 impl 0x6 ver 0x93 clock 2150 MHz)
The physical processor has 4 virtual processors (8-11)
SPARC64-VI... (3 Replies)
Hi all.
I have a question about linux command to find number of CPU and Core.
I usually use the command dmidecode -t processor to find cpu and core numbers . On this machine with Red Hat 4. 0 when I try to insert the command is returned the error
-bash: dmidecode: command not found
I try to... (8 Replies)
Hi,
I am trying to gather cpu core details and used this script - Solaris & Scripting: Script - Find cpu - model / type / count / core / thread / speed - Solaris Sparc
For auuditing purpose, we want to know how many cores are being used by Oracle, because oracle license will be charged on... (2 Replies)
Discussion started by: solaris_1977
2 Replies
LEARN ABOUT X11R4
systemd-machine-id-setup
SYSTEMD-MACHINE-ID-SETUP(1) systemd-machine-id-setup SYSTEMD-MACHINE-ID-SETUP(1)NAME
systemd-machine-id-setup - Initialize the machine ID in /etc/machine-id
SYNOPSIS
systemd-machine-id-setup
DESCRIPTION
systemd-machine-id-setup may be used by system installer tools to initialize the machine ID stored in /etc/machine-id at install time, with
a provisioned or randomly generated ID. See machine-id(5) for more information about this file.
If the tool is invoked without the --commit switch, /etc/machine-id is initialized with a valid, new machined ID if it is missing or empty.
The new machine ID will be acquired in the following fashion:
1. If a valid D-Bus machine ID is already configured for the system, the D-Bus machine ID is copied and used to initialize the machine ID
in /etc/machine-id.
2. If run inside a KVM virtual machine and a UUID is configured (via the -uuid option), this UUID is used to initialize the machine ID.
The caller must ensure that the UUID passed is sufficiently unique and is different for every booted instance of the VM.
3. Similarly, if run inside a Linux container environment and a UUID is configured for the container, this is used to initialize the
machine ID. For details, see the documentation of the Container Interface[1].
4. Otherwise, a new ID is randomly generated.
The --commit switch may be used to commit a transient machined ID to disk, making it persistent. For details, see below.
Use systemd-firstboot(1) to initialize the machine ID on mounted (but not booted) system images.
OPTIONS
The following options are understood:
--root=root
Takes a directory path as argument. All paths operated will be prefixed with the given alternate root path, including the path for
/etc/machine-id itself.
--commit
Commit a transient machine ID to disk. This command may be used to convert a transient machine ID into a persistent one. A transient
machine ID file is one that was bind mounted from a memory file system (usually "tmpfs") to /etc/machine-id during the early phase of
the boot process. This may happen because /etc is initially read-only and was missing a valid machine ID file at that point.
This command will execute no operation if /etc/machine-id is not mounted from a memory file system, or if /etc is read-only. The
command will write the current transient machine ID to disk and unmount the /etc/machine-id mount point in a race-free manner to ensure
that this file is always valid and accessible for other processes.
This command is primarily used by the systemd-machine-id-commit.service(8) early boot service.
--print
Print the machine ID generated or committed after the operation is complete.
-h, --help
Print a short help text and exit.
--version
Print a short version string and exit.
EXIT STATUS
On success, 0 is returned, a non-zero failure code otherwise.
SEE ALSO systemd(1), machine-id(5), systemd-machine-id-commit.service(8), dbus-uuidgen(1), systemd-firstboot(1)NOTES
1. Container Interface
https://www.freedesktop.org/wiki/Software/systemd/ContainerInterface
systemd 237SYSTEMD-MACHINE-ID-SETUP(1)