userselector(7) [mojave man page]
UserSelector(7) BSD Miscellaneous Information Manual UserSelector(7) NAME
UserSelector -- overview and documentation DESCRIPTION
UserSelector is invoked only internally by the CryptoTokenKit framework. It is not intended to be used directly by an end user or an adminis- trator. Unless the string property UserSelectorPath is set with full executable path value in the configuration file ( /etc/SmartcardLogin.plist ), the system UserSelector is used. How CryptoTokenKit framework invokes UserSelector: UserSelector -o operation -u username -i pubkeyhash1[,pubkeyhash2,...] Path and format UserSelector runs in a sandbox which limits its path and file format. A custom UserSelector must be stored in the /Library/CryptoTokenKit directory. The file format of the UserSelector must be binary. Shell scripts are not supported. Supported Operations Map Operation This operation returns a list of users bound with pubkeyhashes from the SmartCard certificates. The username parameter is optional. If set, bindings are returned only for the specified user. The list of one or more comma separated pubkeyhashes is mandatory. Result format: Recognized bindings are returned through stdout. Each binding is placed on a separate line. Each line begins with the pubkeyhash string, fol- lowed by the TAB character ( ) and by the username. Sample: $ UserSelector -o map -i 01234567890123456789,ABCDEF01230123456789,98765432109876543210 ABCDEF01230123456789 user1 98765432109876543210 user2 Bind Operation This operation creates binding between the provided pubkeyhash and username . Result format: Exit code is set to 0 when succeeded, error code otherwise Sample: $ UserSelector -o bind -i ABCDEF01230123456789 -u username1 Unbind Operation This operation removes SmartCard bindings for the provided username If no pubkeyhash is provided, all bindings for that user are removed. If one or more pubkeyhashes are provided, only bindings for these are removed. Result format: Exit code is set to 0 when succeeded, error code otherwise Sample: $ UserSelector -o unbind -u username1 -i ABCDEF01230123456789 Check Operation This operation checks SmartCard bindings for a specific user. It returns 0 on stdout when the user has no SmartCard bindings, or 1 when already does. The username parameter is mandatory. Sample: $ UserSelector -o check -u username1 1 SEE ALSO
SmartCardServices(7), sc_auth(8) macOS Oct 12, 2017 macOS
Check Out this Related Man Page
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)