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
gcore(1)						      General Commands Manual							  gcore(1)

NAME
gcore - get core images of running processes SYNOPSIS
filename] process-id... DESCRIPTION
The command creates a core image of each specified process. By default, the name of the core image file for process-id will be The process information in the core file can be obtained by using debuggers. When the command creates a core image of each specified process, the process is temporarily stopped. Further, when the creation of core image is complete, the process continues to execute. Options Creates the core file with name of the file as If multiple process-id values are specified, filename will be common for all the core image files. See the section. Operands process-id The process ID for which a core image file will be created. RETURN VALUE
Upon completion, exits with one of the following values: A core file was successfully created. An error condition was encountered. In such a case, the creation of a core file is not guaranteed. The error conditions could be because of o A nonexistent or incorrect process ID was specified. o An invalid option was specified. o The current working directory of the process or directory from which was invoked had no write permissions. o The current working directory of the process was not accessible. o The file system is full. EXAMPLES
Example 1 Dump the core image of process 1030 in the file "core.1030". Example 2 Dump the core image of the process 1030 in the file "test.1030". Example 3 Dump the core image of the processes 1030, 1031, 1032, and 1033 in the files "core.1030", "core.1031", "core.1032", "core.1033". Example 4 Dump the core image of the processes 1030, 1031, 1032, and 1033 in the files FILES
Core image file for process-id. (Both where is invoked and the current working directory of the process.) AUTHOR
was developed by Chris Bertin (HP). SEE ALSO
adb(1), gdb(1), kill(1), ttrace(2), a.out(4), core(4). gcore(1)
All times are GMT -4. The time now is 08:45 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy