Sponsored Content
Full Discussion: Lost CPU CORES
Operating Systems Linux Red Hat Lost CPU CORES Post 302554597 by rmokros on Monday 12th of September 2011 12:19:26 PM
Old 09-12-2011
RHEL 6.1 x64

TYAN S7010 two E5530 (4 cores each) on RHEL 6.1 x64
 

7 More Discussions You Might Find Interesting

1. UNIX for Advanced & Expert Users

Lost one cpu should the box crash

I've got a E6500 with 6 cpu's over 3 cpu boards. we lost one cpu should the box keel over ?? I wouldn't have seen this as a Single Point Of Failure Kie (2 Replies)
Discussion started by: kie
2 Replies

2. Shell Programming and Scripting

Is there a way to make bash [or another shell] use all CPU cores to execute a single script?

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)
Discussion started by: ph0enix
16 Replies

3. UNIX for Dummies Questions & Answers

how to run two unix/linux programs on two different cpu cores

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)
Discussion started by: kaaliakahn
1 Replies

4. Solaris

CPU/processor/cores in M4000

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)
Discussion started by: ningy
3 Replies

5. Solaris

Numbers-of-cpu-cores-in-Solaris-10

Hello All, How do I find the number of CPU's, virtual processors in solaris 10? Thank you Sunil Kumar (2 Replies)
Discussion started by: msgforsunil
2 Replies

6. Red Hat

CPU and Cores information

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)
Discussion started by: piccolinomax
8 Replies

7. Solaris

Questions regarding CPU cores vs rctl limit

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
KSC(1)								   User Commands							    KSC(1)

NAME
ksc - Linux kernel module source checker SYNOPSIS
ksc [ -d | --directory ] DIRECTORY ksc [ -k | --ko ] FILE OPTIONS
KSC accepts command-line arguments, and has both a long and short form usage. You can use either style or combine them to specify options. When the tool is run with kernel module sources it checks for all four architectures, and when run with binary kernel modules, it checks for the specific architecture for which the binary was built. Valid RHEL whitelist releases are rhel6.0, rhel6.1, rhel6.2, rhel6.3, rhel6.4 -h, --help show this help message and exit -c CONFIG, --config=CONFIG path to the local ksc.conf file. If not specified the tool tries to read from ~/ksc.conf and if that is also not found then from /etc/ksc.conf -d DIRECTORY, --directory=DIRECTORY path to the directory -i, --internal to create text files to be used internally. -k KO, --ko=KO path to the ko file. You should either use -d or -k to run the KSC tool, but not both. If both -d and -k option is used at the same time then only -d is used and the -k option is discarded. -n RELEASENAME, --name=RELEASENAME Red Hat release against which the bug is to be filed. Default value is 6.5 -p PREVIOUS, --previous=PREVIOUS path to the previous resultset file and submit it as a bug to Red Hat Bugzilla. -r RELEASE, --release=RELEASE RHEL whitelist release used for comparison -s, --submit Submits the report to the Red Hat bugzilla (https://bugzilla.redhat.com). The credentials need to be in the /etc/ksc.conf file. The tool will prompt for bugzilla password. The configuration file looks like below: [bugzilla] user=user@redhat.com partner=partner-name partnergroup=partner-group server=https://bugzilla.redhat.com/xmlrpc.cgi -v, --version Prints KSC version number ksc - Version 0.9.11 Feb 2014 KSC(1)
All times are GMT -4. The time now is 10:27 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy