Sponsored Content
Operating Systems Solaris Assign a process to a core on start Post 302910718 by achenle on Sunday 27th of July 2014 04:48:29 PM
Old 07-27-2014
man psrset
 

10 More Discussions You Might Find Interesting

1. Shell Programming and Scripting

how to start a process and make it sleep for 5 mins and then kill that process

how to start a process and make it sleep for 5 mins and then kill that process (6 Replies)
Discussion started by: shrao
6 Replies

2. UNIX for Dummies Questions & Answers

Getting core id, physical id of running process

Hi All, I need a help. I need to know: 1. the individual core id, physical id of a running process on multicore inside a program. The system file /proc/cpuinfo shows all the ids of all the processes. But I need to know runtime, what exact core id and physical id , the running process has.... (0 Replies)
Discussion started by: debrajde
0 Replies

3. Solaris

coreadm diasble a process from core dumping

Hello All Is it possible to disable a specific process from core dumping ? In my environment I have 2 bespoke application processes which needs to be stopped from core dumping but any other process should be allowed to core dump. If I do : coreadm -d process it will stop all per processes... (3 Replies)
Discussion started by: baner_n
3 Replies

4. UNIX for Dummies Questions & Answers

How to force core dump of a process

We have an application that terminates with segmentation violation errors in the logs. No source code is available since this is a third party software that is way past its maintenance life cycle. Under these circumstances is there a way to force a core dump of the process for further analysis?? ... (3 Replies)
Discussion started by: Un1xNewb1e
3 Replies

5. Shell Programming and Scripting

Script - How to automatically start another process when the previous process ends?

Hi all, I'm doing automation task for my team and I just started to learn unix scripting so please shed some light on how to do this: 1) I have 2 sets of datafiles - datafile A and B. These datafiles must be loaded subsequently and cannot be loaded concurrently. 2) So I loaded datafile A... (10 Replies)
Discussion started by: luna_soleil
10 Replies

6. Programming

how to monitor the child process on which cpu core

Hi all. Sorry to express my questions wrongly in my early post,I repost my question again here. My pc has dual core, I wirte an application with two process, parents process and child process. My quetion is how to realize :if the child process is on core 0,it will tell me I'm on core 0,if it... (1 Reply)
Discussion started by: yanglei_fage
1 Replies

7. UNIX for Dummies Questions & Answers

Script to start background process and then kill process

What I need to learn is how to use a script that launches background processes, and then kills those processes as needed. The script successfully launches the script. But how do I check to see if the job exists before I kill it? I know my problem is mostly failure to understand parameter... (4 Replies)
Discussion started by: holocene
4 Replies

8. Red Hat

Process does not dump any core files when crashed even if coredumpsize is unlimited

Hello Im using redhat and try to debug my application , its crashes and in strace I also see it has problems , but I can't see any core dump I configured all the limit ( im using .cshrc ) and it looks like this : cputime unlimited filesize unlimited datasize unlimited... (8 Replies)
Discussion started by: umen
8 Replies

9. Shell Programming and Scripting

Get the process/thread running on which core

I use top -H -p 1256 to show process 1256, and then press "f" then press "j" to display it is running on which core, is there a better mothed, I want to be automated to get this (1 Reply)
Discussion started by: yanglei_fage
1 Replies

10. Red Hat

Core Dump of a process in Red Hat Linux 5.9

Hello All, I am new joiner of this forum.I am new to Linux shell scripting. At present I have identified 1 application which stalls very frequently (PID is say xyz) and I am not having much information in its application log to identify the root cause of stalling. I need to take the core dump... (19 Replies)
Discussion started by: Anjan Ganguly
19 Replies
psrset(1M)                                                System Administration Commands                                                psrset(1M)

NAME
psrset - creation and management of processor sets SYNOPSIS
psrset -a [-F] processor_set_id processor_id... psrset -b processor_set_id pid [/lwpid]... psrset -c [-F] [processor_id...] psrset -d processor_set_id... psrset -e processor_set_id command [argument(s)] psrset -f processor_set_id psrset [-i] [processor_set_id...] psrset -n processor_set_id psrset -p [processor_id...] psrset [-q] [pid [/lwpid]...] psrset -Q [processor_set_id...] psrset -r [-F] processor_id... psrset -u pid [/lwpid]... psrset -U [processor_set_id...] DESCRIPTION
The psrset utility controls the management of processor sets. Processor sets allow the binding of processes or LWPs to groups of proces- sors, rather than just a single processor. Processors assigned to processor sets can run only LWPs that have been bound to that processor set. This command cannot be used to modify processor disposition when pools are enabled. Use pooladm(1M) and poolcfg(1M) to modify processor set configuration through the resource pools facility. OPTIONS
The following options are supported: -a Assign the specified processors to the specified processor set. With the additional -F option, all LWPs bound to the specified processors will be unbound prior to changing processor sets. This option is restricted to use by the super-user. -b Bind all or a subset of the LWPs of the specified processes to the specified processor set. LWPs bound to a processor set are restricted to run only on the processors in that set. Processes can only be bound to non-empty processor sets, that is, processor sets that have had processors assigned to them. Bindings are inherited, so new LWPs and processes created by a bound LWP have the same binding. Binding an interactive shell to a processor, for example, binds all commands executed by the shell. This option is restricted to use by the super-user. -c Create a new processor set and displays the new processor set ID. With the additional -F option, all LWPs bound to the specified processors will be unbound prior to assigning them to the processor set being created. If a list of processors is given, it also attempts to assign those processors to the processor set. If this succeeds, the proces- sors are idle until LWPs are bound to the processor set. This option is restricted to use by the super-user. Only a limited number of processor sets can be active (created and not destroyed) at a given time. This limit is always be greater than the number of processors in the system. If the -c option is used when the maximum number of processor sets is already active, the command fails. The following format is used for the first line of output of the -c option when the LC_MESSAGES locale category specifies the "C" locale. In other locales, the strings created, processor, and set can be replaced with more appropriate strings corresponding to the locale. "created processor set %d " processor set ID -d Remove the specified processor set, releasing all processors and processes associated with it. This option is restricted to use by the super-user. -e Execute a command (with optional arguments) in the specified processor set. The command process and any child processes are executed only by processors in the processor set. This option is restricted to use by the super-user. -f Disables interrupts for all processors within the specified processor set. See psradm(1M). If some processors in the set cannot have their interrupts disabled, the other processors still have their interrupts disabled, and the command reports an error and return non-zero exit status. This option is restricted to use by the super-user. -F Forces the specified processor set operation by unbinding all threads bound to the specified processor. Only the -a or the -r option can be used in combination with this option. Administrators are encouraged to use the -Q option for pbind(1M) to find out which threads will be affected by such operation. -i Display a list of processors assigned to each named processor set. If no argument is given, a list of all processor sets and the processors assigned to them is displayed. This is also the default operation if the psrset command is not given an option. -n Enable interrupts for all processors within the specified processor set. See psradm(1M). This option is restricted to use by the super-user. -p Display the processor set assignments for the specified list of processors. If no argument is given, the processor set assignments for all processors in the system is given. -q Display the processor set bindings of the specified processes or of all processes. If a process is composed of multiple LWPs which have different bindings and the LWPs are not explicitly specified, the bindings of only one of the bound LWPs is displayed. The bindings of a subset of LWPs can be displayed by appending "/lwpids" to the process IDs. Multiple LWPs may be selected using "-" and "," delimiters. See EXAMPLES. -Q Display the LWPs bound to the specified list of processor sets, or all LWPs with processor set bindings. -r Remove a list of processors from their current processor sets. Processors that are removed return to the general pool of proces- sors. Processors with LWPs bound to them using pbind(1M) can be assigned to or removed from processor sets using the -F option. This option is restricted to use by the super-user. -u Remove the processor set bindings of a subset or all the LWPs of the specified processes, allowing them to be executed on any on- line processor if they are not bound to individual processors through pbind. The super-user can unbind any process or LWP from any active processor set. Other users can unbind processes and LWPs from proces- sor sets that do not have the PSET_NOESCAPE attribute set. In addition, the user must have permission to control the affected pro- cesses; the real or effective user ID of the user must match the real or saved user ID of the target processes. -U Removes the bindings of all LWPs bound to the specified list of processor sets, or to any processor set if no argument is speci- fied. OPERANDS
The following operands are supported: pid Specify pid as a process ID. lwpid The set of LWPIDs of the specified process to be controlled or queried. The syntax for selecting LWP IDs is as fol- lows: 2,3,4-8 LWP IDs 2, 3, and 4 through 8 -4 LWPs whose IDs are 4 or below 4- LWPs whose IDs are 4 or above processor_id Specify processor_id as an individual processor number (for example, 3), multiple processor numbers separated by spaces (for example, 1 2 3), or a range of processor numbers (for example, 1-4). It is also possible to combine ranges and (individual or multiple) processor_ids (for example, 1-3 5 7-8 9). processor_set_id Specify processor_set_id as a processor set ID. EXIT STATUS
The following exit values are returned: 0 Successful completion. non-0 An error occurred. ATTRIBUTES
See attributes(5) for descriptions of the following attributes: +-----------------------------+-----------------------------+ | ATTRIBUTE TYPE | ATTRIBUTE VALUE | +-----------------------------+-----------------------------+ |Availability |SUNWcsu | +-----------------------------+-----------------------------+ |Stability Level |Stable | +-----------------------------+-----------------------------+ SEE ALSO
pbind(1M), pooladm(1M), poolcfg(1M), psradm(1M), psrinfo(1M), processor_bind(2), processor_info(2), pset_bind(2), pset_create(2), pset_info(2), sysconf(3C), libpool(3LIB), attributes(5) DIAGNOSTICS
The following output indicates that the specified process did not exist or has exited: psrset: cannot query pid 31: No such process The following output indicates that the user does not have permission to bind the process: psrset: cannot bind pid 31: Not owner The following output indicates that the user does not have permission to assign the processor: psrset: cannot assign processor 4: Not owner The following output indicates that the specified processor is not on-line, or the specified processor does not exist. psrset: cannot assign processor 8: Invalid argument The following output indicates that an LWP in the specified process is bound to a processor and cannot be bound to a processor set that does not include that processor: psrset: cannot bind pid 67: Device busy The following output indicates that the specified processor could not be added to the processor set. This can be due to bound LWPs on that processor, or because that processor cannot be combined in the same processor set with other processors in that set, or because the proces- sor is the last one in its current processor set: psrset: cannot assign processor 7: Device busy The following output indicates that the specified processor set does not exist: psrset: cannot execute in processor set 8: Invalid argument The following output indicates that the maximum number of processor sets allowed in the system is already active: psrset: cannot create processor set: Not enough space The following output indicates that the pools facility is active. psrset: cannot assign processor 7: Operation not supported psrset: cannot bind pid 31: Operation not supported psrset: cannot bind pid 31: Operation not supported psrset: could not create processor set: Operation not supported psrset: could not remove processor set 1: Operation not supported psrset: cannot exec in processor set 1: Operation not supported psrset: cannot remove processor 7: Operation not supported psrset: cannot unbind pid 31: Operation not supported SunOS 5.10 17 Aug 2004 psrset(1M)
All times are GMT -4. The time now is 08:08 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy