SCF Reference Manual for the Kernel Subsystem

Table 13 SCF Commands and Object Types for the Kernel Subsystem (continued)
Object Types
SUBSYSSERVERNETPROCESSnullCommand
XXXXNAMES
--XX--START
XXX--STATUS
--X----STOP
XXXXVERSION
X = The command currently supports this object type.
-- = The command does not support this object type.
Sensitive and Nonsensitive Commands
SCF commands are either sensitive or nonsensitive.
Sensitive SCF commands can change subsystem behavior. Only a super-group user (255,n) can
issue a sensitive command. SUPER.SUPER may issue any sensitive command against any generic
process, regardless of its owner. Additionally, the user, who is a member of the new security group
SECURITY-PERSISTENCE-ADMIN, would also be able to issue any sensitive commands; i.e., it will
have same privileges as SUPER.SUPER for managing persistent processes. For other super-group
users, there are additional restrictions described below for a subset of sensitive commands.
Nonsensitive SCF commands request information or status but do not affect operation. SCP does
not perform any security checking on these commands. Any user may issue a nonsensitive command.
Table 14 lists the sensitive and nonsensitive SCF commands for the Kernel subsystem.
Table 14 Sensitive and Nonsensitive SCF Commands
Nonsensitive CommandsSensitive Commands
INFOABORT
NAMESADD
STATUSALTER
VERSIONCONTROL
DELETE
START
STOP
ABORT
A super-group user (255,n) can ABORT any generic process owned by any user.
ADD
A super-group user (255,n) can ADD a generic process. Any generic process added by a
super-group user other than SUPER.SUPER automatically is owned by the user adding the
process. Only SUPER.SUPER can add a generic process belonging to a non-super-group user.
ALTER
A super-group user (255,n) can ALTER a generic process owned by any user. The following
attributes cannot be altered for a process which is owned by any other user:
• USERID
• PROGRAM
74 SCF Commands for the Kernel Subsystem