chserver Command

Commands Reference, Volume 1

chserver Command

Purpose

Changes a subserver definition in the subserver object class.

Syntax

chserver -t OldSubserver [ -c CodePoint ] [ -s NewSubsystem ] [ -t NewSubserver ]

Description

The chserver command modifies an existing subserver definition in the subserver object class. It can change subserver types, the owning subsystem, or the subserver code point.

Flags

-c CodePoint	Specifies the CodePoint integer that identifies the subserver. This is the value used by the subsystem to recognize the subserver. The chserver command is unsuccessful if the CodePoint already exists for the existing subsystem name and no new subsystem name is entered. It is also unsuccessful if the NewSubsystem name and subserver CodePoint exist in the subserver object class. The limit for the CodePoint storage is the same as a short integer (1 through 32,768).
-s NewSubsystem	Specifies the name that uniquely identifies the NewSubsystem to the subserver it belongs to. The chserver command is unsuccessful if one of the following occurs: The NewSubsystem name is not known in the subsystem object class. The NewSubsystem name is known in the subsystem object class but uses signals as its communication method. The NewSubsystem name already exists with the existing subserver CodePoint value in the Subserver Type object class, and no subserver CodePoint value is entered. A new subserver CodePoint is entered, with the NewSubsystem name and subserver CodePoint already existing in the Subserver Type object class.
-t NewSubserver	Specifies the name that uniquely identifies the NewSubserver. The chserver command is unsuccessful if the NewSubserver type is already known in the subserver object class.
-t OldSubserver	Specifies the name that uniquely identifies the existing subserver. The chserver command is unsuccessful if the OldSubserver type is not known in the subserver object class.

Security

Auditing Events: If the auditing subsystem has been properly configured and is enabled, the chserver command will generate the following audit record (event) every time the command is executed:

Event	Information
SRC_Chserver	Lists in an audit log the name of the subsystem and the fields that have been changed.

See "Setting up Auditing" in AIX Version 4.3 System Management Guide: Operating System and Devices for more details about how to properly select and group audit events, and how to configure audit event data collection.

Examples

To change the subserver type, enter:
```
chserver -t old -t new
```
This changes the subserver type from the old subserver type to the new subserver type.
To change the owning subsystem, enter:
```
chserver -t old -s srctest
```
This changes the owning subsystem to srctest.
To change the subserver type, subsystem, and subserver code point, enter:
```
chserver -t old -t new -s srctest -c 1234
```
This changes the subserver type from the old to the new subserver type, the owning subsystem to srctest, and the subserver code point to 1234.

Files

/etc/objrepos/SRCsubsys	Specifies the SRC Subsystem Configuration object class.
/etc/objrepos/SRCsubsvr	Specifies the SRC Subserver Configuration object class.

Related Information

The auditpr command, mkserver command, rmserver command, startsrc command, stopsrc command, traceson command, tracesoff command.

Auditing Overview in AIX Version 4.3 System Management Concepts: Operating System and Devices.

System Resource Controller Overview in AIX Version 4.3 System Management Concepts: Operating System and Devices.

Defining Your Subsystem to the SRC in AIX General Programming Concepts: Writing and Debugging Programs.

System Resource Controller (SRC) Overview for Programmers in AIX General Programming Concepts: Writing and Debugging Programs.