Guardian Procedure Calls Reference Manual (G06.25+)

Guardian Procedure Calls (P)
Guardian Procedure Calls Reference Manual—522629-013
12-158
PROCESS_SETINFO_ Procedure
Considerations
•
The caller of PROCESS_SETINFO_
When PROCESS_SETINFO_ is called on a Guardian process, the caller must be
the super ID, the group manager of the process access ID, or a process with the
same process access ID as the process or process pair whose attribute is being
changed. For information about the process access ID, refer to the description
under “Considerations” for the PROCESS_GETINFO_ procedure and the
Guardian User’s Guide.
When PROCESS_SETINFO_ is called on an OSS process, the security rules that
apply are the same as those that apply when calling the OSS
kill() function.
See the
kill(2) function reference pages either online or in the Open System
Services System Calls Reference Manual for details.
The caller must be local to the same system as the specified process. A process
is considered to be local to the system on which its creator is local. A process is
considered to be remote, even if it is running on the local system, if its creator is
remote. (In the same manner, a process running on the local system whose
creator is also running on the local system might still be considered remote
because its creator’s creator is remote.)
A remote process running on the local system can become a local process by
successfully logging on to the local system using a call to the
USER_AUTHENTICATE_ procedure (or VERIFYUSER). After a process logs on
to the local system, any processes that it creates are considered local.
•
Attributes that can be set or cleared by privileged callers only
Several attributes can be set or cleared (set to 0) by privileged callers only, as
follows:
item 45 (logged-on state) must be priv to set, nonpriv can clear
item 50 (Safeguard-authenticated logon) must be priv to set or clear
item 70 (propagate logon) must be priv to set, nonpriv can clear
item 75 (nice() caller’s value) must be priv to set or clear
•
Mom’s process handle
Specifying item 40 (mom’s process handle) is analogous to calling STEPMOM on a
process. The caller becomes the new mom of the specified process, and will
receive the process deletion system message when the process terminates. The
former mom will not receive a process deletion system message.
specifier is
ignored, as this operation applies only to a single target process.
set-value is
ignored, because the caller must be doing the adoption on its own behalf; no third-
party adoptions are permitted.
A process should not alter the mom of a member of a named process pair by
calling either PROCESS_SETINFO_ or STEPMOM. This causes errors and
interferes with operation, as correct operation depends upon each member of a
named process pair being the other member’s mom.