89 writable by the user.
90
91
92 EINVAL
93 An invalid processor set ID was specified; or idtype was
94 not P_PID, P_LWPID, P_PROJID, P_TASKID, P_ZONEID, or P_CTID.
95
96
97 ENOTSUP
98 The pools facility is active. See pooladm(1M) and
99 pool_set_status(3POOL) for information about enabling and
100 disabling the pools facility. Processes can be bound to
101 pools using the poolbind(1M) utility or the
102 pool_set_binding(3POOL) function.
103
104 Binding a system process to a processor set is not
105 supported.
106
107
108 EPERM
109 The {PRIV_PROC_OWNER} is not asserted in the effecive set of
110 the calling process and either the real or effective user ID
111 of the calling process does not match the real or effective
112 user ID of one of the LWPs being bound, or the processor set
113 from which one or more of the LWPs are being unbound has the
114 PSET_NOESCAPE attribute set and {PRIV_SYS_RES_CONFIG) is not
115 asserted in the effective set of the calling process. See
116 pset_setattr(2) for more information about processor set
117 attributes.
118
119
120 ESRCH
121 No processes, LWPs, or tasks were found to match the
122 criteria specified by idtype and id.
123
124
125 ATTRIBUTES
126 See attributes(5) for descriptions of the following attributes:
127
128
129
130
131 +--------------------+-------------------+
132 | ATTRIBUTE TYPE | ATTRIBUTE VALUE |
133 +--------------------+-------------------+
134 |Interface Stability | Committed |
135 +--------------------+-------------------+
136 |MT-Level | Async-Signal-Safe |
137 +--------------------+-------------------+
|
89 writable by the user.
90
91
92 EINVAL
93 An invalid processor set ID was specified; or idtype was
94 not P_PID, P_LWPID, P_PROJID, P_TASKID, P_ZONEID, or P_CTID.
95
96
97 ENOTSUP
98 The pools facility is active. See pooladm(1M) and
99 pool_set_status(3POOL) for information about enabling and
100 disabling the pools facility. Processes can be bound to
101 pools using the poolbind(1M) utility or the
102 pool_set_binding(3POOL) function.
103
104 Binding a system process to a processor set is not
105 supported.
106
107
108 EPERM
109 The {PRIV_PROC_OWNER} is not asserted in the effective set
110 of the calling process and either the real or effective user
111 ID of the calling process does not match the real or
112 effective user ID of one of the LWPs being bound, or the
113 processor set from which one or more of the LWPs are being
114 unbound has the PSET_NOESCAPE attribute set and
115 {PRIV_SYS_RES_CONFIG) is not asserted in the effective set
116 of the calling process. See pset_setattr(2) for more
117 information about processor set attributes.
118
119
120 ESRCH
121 No processes, LWPs, or tasks were found to match the
122 criteria specified by idtype and id.
123
124
125 ATTRIBUTES
126 See attributes(5) for descriptions of the following attributes:
127
128
129
130
131 +--------------------+-------------------+
132 | ATTRIBUTE TYPE | ATTRIBUTE VALUE |
133 +--------------------+-------------------+
134 |Interface Stability | Committed |
135 +--------------------+-------------------+
136 |MT-Level | Async-Signal-Safe |
137 +--------------------+-------------------+
|