Open System Services Management and Operations Guide (G06.25+, H06.03+)

Managing Servers

Open System Services Management and Operations Guide—527191-002

4-46

Reconfiguring a Network Services Server

Network services servers ignore changes to configuration files while they are running.

Configuration files such as /etc/inetd.conf can be edited while the servers are

running. However, to make configuration changes take effect, you must:

1. Warn your users. You can use a method similar to the one described under

Manually Stopping the OSS File System and the OSS Environment on page 2-3.

2. Stop or interrupt each process separately by identifying its OSS process ID (PID)

using the ps command from an OSS shell prompt and then issuing a kill

command.

For example, to interrupt the inetd process, enter commands similar to the

following:

kill -s SIGHUP 4291

where 4291 is the OSS process ID of the inetd process. This form of the kill

command sends the SIGHUP signal to the inetd process; inetd rereads its

current configuration file in response to this signal and continues to run using the

new configuration.

Removing a Server

How and when you remove a server depends on the type of server. You cannot

remove the OSS sockets local server, the OSS message-queue server, or an OSS

transport agent server.

•

Removing an OSS Name Server on page 4-46

•

Removing a Network Services Server on page 4-47

Other servers used by OSS applications require separate procedures. For more

information, see the manual appropriate for a specific server.

Removing an OSS Name Server

You remove an OSS name server by removing its entry in the Enscribe database

ZOSSSERV file.

1. Make sure that you are a member of the super group (255,nnn).

2. Use the following OSS Monitor SCF command to determine which filesets are

managed by the OSS name server that you want to remove:

INFO FILESET $ZPMON.*, DETAIL

Note. You cannot remove the OSS name server for the root fileset, $ZPNS.