Sponsored Content
Full Discussion: Restricting CPU Core Access
Operating Systems Solaris Restricting CPU Core Access Post 302363772 by boneyard on Wednesday 21st of October 2009 10:04:43 AM
Old 10-21-2009
Quote:
Originally Posted by jlliagre
With a 8 core T2000, each core supporting 4 threads, you have 32 virtual CPUs.

Have a look at
Code:
psrinfo -v

output.
Right, i get you. You cant limit core's as such, you limit the number of virual CPU's ie 4CPU's = 1core.

Excellent stuff, i get it....took a while though eh Smilie

Thanks again, thats great

Cheers
 

10 More Discussions You Might Find Interesting

1. Cybersecurity

restricting access...

restricted access... Hi I need to restrict users shell access to only $HOME under /home for each user. I don't want them getting out of their own directories. From what I understand chroot is something I could use, but I want to avoid this since it involves creating symbolic links to a number... (9 Replies)
Discussion started by: alwayslearningunix
9 Replies

2. UNIX for Dummies Questions & Answers

Restricting access

I need to create a user that only has access to 1 directory (e.g. /vol/mita/test). The user needs to be able to rsh into that directory to run a script. The user should not be able to navigate to any other directories above /vol/mita/test. Any help would be appreciated! (4 Replies)
Discussion started by: ngagne
4 Replies

3. Solaris

restricting access

Hi All, I'm on Solaris 8, I need to provide Read-only access to a user to 2 directories only. Using rsh (restricted shell) as the user's login shell, I can restrict the user's access to a certain directory only, but how can I set in such a way that the user can access only the 2 directories... (4 Replies)
Discussion started by: max_min
4 Replies

4. UNIX for Advanced & Expert Users

restricting root access

I'm the admin in a shop in which my developers have and use the root account, all UNIX newbies. I've been unable to convince management myself that this is an unacceptable practice. I've looked in a couple books I have and can't find any chapters, discussions, etc that make the argument that... (2 Replies)
Discussion started by: keith.m
2 Replies

5. Solaris

restricting access to a server

We want to secure access to a server by restricting the number of users who can login to it. Our users are NIS users. Only few of them can telnet/ssh this server. Do you have any idea on how to implement that? thanks. (1 Reply)
Discussion started by: melanie_pfefer
1 Replies

6. UNIX for Dummies Questions & Answers

Setting permissions and restricting access

Hi all, I have user called "Z". The home directory is /home/Z. I have another directory /home/Z/OP. Within /home/Z/OP, i have 2 directories /home/Z/OP/OP1 and /home/Z/OP2. I want to restrict access for Z to only access /home/Z/OP and /home/Z/OP1 and /home/Z/OP2. What kind of... (4 Replies)
Discussion started by: new2ss
4 Replies

7. UNIX for Advanced & Expert Users

Restricting access to code

Hi All, I am facing a problem, regarding code security on a server. We have configured a server which contains our code (ear present in jboss/server/xyz/deploy) in it, and need to bind the code to the server itself so that no one can take the code out of the. the problem is that the password of... (3 Replies)
Discussion started by: akshay61286
3 Replies

8. Solaris

Restricting FTP access for a particular directory

Dear All, I have created a user called "x" who is allowed only to FTP and it is working fine. Here my problem is, I want to give access to a particular directory say for eg:- /dump/test directory. I don't find any option in the useradd command to restrict access to this particular directory only... (1 Reply)
Discussion started by: Vijayakumarpc
1 Replies

9. UNIX for Dummies Questions & Answers

Restricting SFTP access

Hello, I am using MySecureShell to chroot all sftp accesses. The problem that I have is that my boss does not want root to be able to use sftp. Root should still be able to ssh. Any ideas? (2 Replies)
Discussion started by: mojoman
2 Replies

10. Solaris

Restricting commands & access

Dear all, I am administering a DC environment of over 100+ Solaris servers used by various teams including Databases. Every user created on the node belonging to databases is assigned group staff(10) . I want that all users belonging to staff should NOT be able to execute certain system... (6 Replies)
Discussion started by: Junaid Subhani
6 Replies
LSCPU(1)							   User Commands							  LSCPU(1)

NAME
lscpu - display information about the CPU architecture SYNOPSIS
lscpu [-a|-b|-c] [-x] [-s directory] [-e[=list]|-p[=list]] lscpu -h|-V DESCRIPTION
lscpu gathers CPU architecture information from sysfs and /proc/cpuinfo. The command output can be optimized for parsing or for easy read- ability by humans. The information includes, for example, the number of CPUs, threads, cores, sockets, and Non-Uniform Memory Access (NUMA) nodes. There is also information about the CPU caches and cache sharing, family, model, bogoMIPS, byte order, and stepping. Options that result in an output table have a list argument. Use this argument to customize the command output. Specify a comma-separated list of column labels to limit the output table to only the specified columns, arranged in the specified order. See COLUMNS for a list of valid column labels. The column labels are not case sensitive. Not all columns are supported on all architectures. If an unsupported column is specified, lscpu prints the column but does not provide any data for it. COLUMNS CPU The logical CPU number of a CPU as used by the Linux kernel. CORE The logical core number. A core can contain several CPUs. SOCKET The logical socket number. A socket can contain several cores. BOOK The logical book number. A book can contain several sockets. NODE The logical NUMA node number. A node may contain several books. CACHE Information about how caches are shared between CPUs. ADDRESS The physical address of a CPU. ONLINE Indicator that shows whether the Linux instance currently makes use of the CPU. CONFIGURED Indicator that shows if the hypervisor has allocated the CPU to the virtual hardware on which the Linux instance runs. CPUs that are configured can be set online by the Linux instance. This column contains data only if your hardware system and hypervisor sup- port dynamic CPU resource allocation. POLARIZATION This column contains data for Linux instances that run on virtual hardware with a hypervisor that can switch the CPU dispatching mode (polarization). The polarization can be: horizontal The workload is spread across all available CPUs. vertical The workload is concentrated on few CPUs. For vertical polarization, the column also shows the degree of concentration, high, medium, or low. This column contains data only if your hardware system and hypervisor support CPU polarization. OPTIONS
-a, --all Include lines for online and offline CPUs in the output (default for -e). This option may only be specified together with option -e or -p. -b, --online Limit the output to online CPUs (default for -p). This option may only be specified together with option -e or -p. -c, --offline Limit the output to offline CPUs. This option may only be specified together with option -e or -p. -e, --extended[=list] Display the CPU information in human readable format. If the list argument is omitted, all columns for which data is available are included in the command output. When specifying the list argument, the string of option, equal sign (=), and list must not contain any blanks or other whitespace. Examples: '-e=cpu,node' or '--extended=cpu,node'. -h, --help Display help information and exit. -p, --parse[=list] Optimize the command output for easy parsing. If the list argument is omitted, the command output is compatible with earlier versions of lscpu. In this compatible format, two commas are used to separate CPU cache columns. If no CPU caches are identified the cache column is omitted. If the list argument is used, cache columns are separated with a colon (:). When specifying the list argument, the string of option, equal sign (=), and list must not contain any blanks or other whitespace. Examples: '-p=cpu,node' or '--parse=cpu,node'. -s, --sysroot directory Gather CPU data for a Linux instance other than the instance from which the lscpu command is issued. The specified directory is the system root of the Linux instance to be inspected. -x, --hex Use hexadecimal masks for CPU sets (for example 0x3). The default is to print the sets in list format (for example 0,1). -V, --version Display version information and exit. BUGS
The basic overview of CPU family, model, etc. is always based on the first CPU only. Sometimes in Xen Dom0 the kernel reports wrong data. On virtual hardware the number of cores per socket, etc. can be wrong. AUTHOR
Cai Qian <qcai@redhat.com> Karel Zak <kzak@redhat.com> Heiko Carstens <heiko.carstens@de.ibm.com> SEE ALSO
chcpu(8) AVAILABILITY
The lscpu command is part of the util-linux package and is available from ftp://ftp.kernel.org/pub/linux/utils/util-linux/. util-linux January 2013 LSCPU(1)
All times are GMT -4. The time now is 11:00 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy