Safeguard Administrator's Manual (G06.24+, H06.03+)
Table Of Contents
- What’s New in This Manual
- About This Manual
- 1 Introduction
- 2 Controlling User Access
- Introduction
- Using SAFECOM to Establish a Local User Community
- Using SAFECOM to Manage User Access to Your System
- Changing the Owner of a User Authentication Record
- Granting a User Temporary Access to Your System
- Requiring Users to Change Their Passwords
- Granting a Grace Period for Changing an Expired Password
- Forcing Immediate Expiration of a User’s Password
- Freezing a User's Ability to Access the System
- Specifying Auditing for a User ID
- Deleting Users
- Deleting Administrative Groups
- Using SAFECOM to Establish a Network of Users
- Using Safeguard With Nodes With Standard Security
- Identifying Network Users
- Granting a Network User Access to Objects on Your System
- Establishing a Community of Network Users
- Changes to the PAID During a User’s Session
- Additional Considerations for Aliases and Groups
- Additional Considerations for ACCESS with Network Specific Subject IDs
- Establishing Default Protection for a User's Disk Files
- Specifying a Default Command Interpreter for a User
- Establishing Guardian Defaults
- Assigning an Alias to a User
- 3 Managing User Groups
- 4 Securing Volumes and Devices
- 5 OBJECTTYPE Control
- 6 Managing Security Groups
- 7 Securing Terminals
- 8 Warning Mode
- 9 Configuration
- Safeguard Attributes
- Configuring User Authentication
- Configuring Password Control
- Configuring Device Control
- Configuring Process Control
- Configuring Disk-File Control
- Configuring Safeguard Auditing
- Configuring a Default Command Interpreter
- Configuring Communication With $CMON
- Configuring Logon Dialog
- Configuring Exclusive Access at Safeguard Terminals
- Configuring Warning Mode
- Configuring Persistence
- Configuring Attributes for Node Specific Subjects in ACLs
- 10 Installation and Management
- Safeguard Components
- Process Considerations for the SMP and SAFECOM
- Safeguard Subsystem Management Commands
- General Installation Procedure
- Installing the Safeguard Software
- Starting the SMP
- Converting to the Safeguard Subsystem
- Updating the Safeguard Software
- Guidelines for Securing the Safeguard Subsystem
- Monitoring the Safeguard Subsystem
- A SAFECOM Command Syntax
- Index
Installation and Management
Safeguard Administrator’s Manual—523317-013
10-3
Process Considerations for the SMP and SAFECOM
Process Considerations for the SMP and
SAFECOM
The system uses a process identification number (PIN) to identify a process. When the
system creates a new process, it assigns a PIN to the process. Processes on a system
running D-series or G-series RVUs can have either a high or a low PIN as:
•
A low PIN ranges from 0 through 254.
•
A high PIN ranges from 256 through the maximum number supported by the
processor.
PIN 255 is used only for a synthetic process ID, which is described in the Guardian
Application Conversion Guide.
By default, the SMP and SAFECOM run at low PINs. The SMONs run at high PINs. If
you have a single system running D-series or G-series RVUs or a network that
consists only of systems running D-series and G-series RVUs, you can optionally allow
the SMP and SAFECOM to run at high PINs by using the SET HIGHPIN option of
Binder.
However, if you have a network of mixed systems running C-series RVUs and D-series
or G-series RVUs, you should run SAFECOM and the SMP at low PINs. If you allow
these processes to run at high PINs, they cannot communicate with the low PIN
processes on systems running C-series RVUs.
Swap Space Migration Considerations
The SMON processes now require additional swap space on each processor. The
space is needed for an allocated flat data segment used for cache (for temporary
storage of pattern protection records) This cache improves performance considerably.
The SMONs require as much as an additional 64MB of virtual memory. System
administrators must ensure that enough swap space is available on each processor for
this new feature.
Note. Even if CHECK-DISKFILE-PATTERN is OFF, the additional swap space is still required.