Open System Services Management and Operations Guide (G06.29+, H06.07+)

Managing Servers
Open System Services Management and Operations Guide—527191-005
4-50
Removing a Network Services Server
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
See the INFO FILESET Command on page 12-48 for a description of the output.
3. Use the OSS Monitor SCF ALTER FILESET Command on each fileset managed
by the OSS name server you want to remove to change its NAMESERVER entry to
specify another OSS name server.
4. Warn your users to make sure that all their files in affected filesets are closed and
all OSS shell sessions using those filesets are terminated. 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.
5. Use the OSS Monitor SCF STOP FILESET Command on each fileset managed by
the OSS name server you want to remove.
The OSS name server stops itself as soon as the last fileset it was managing
stops.
6. Use the OSS Monitor SCF START FILESET Command on each fileset formerly
managed by the OSS name server you want to remove.
7. Use the OSS Monitor SCF DELETE SERVER Command to remove the stopped
OSS name server from your configuration.
8. If your site uses the STARTOSS utility and the deleted OSS name server serviced
a deleted fileset, you should also delete the fileset name from the OSSINFIL file.
See OSSINFIL File on page C-19 for more information.
Removing a Network Services Server
Stopping the inetd, lwresd, or named server effectively removes that server from
the OSS environment. See Stopping a Network Services Server on page 4-45 for more
information on stopping the inetd, lwresd, or named process.
To remove the remote shell server rshd or the remote execution server rexecd, edit
the /etc/inetd.conf file to delete or comment out the entry for rshd or rexecd.
Although portmap and rpcinfo are used by products in the OSS environment, they
are not OSS processes and cannot be removed from the OSS environment. Stopping
them in the Guardian environment effectively removes then from the node.
Troubleshooting a Server
When you have problems managing a server, follow this general procedure:
1. Check the messages from the OSS Monitor that are sent to your terminal. If you
redirect such messages to a log file, check the log file for its most recent entries.
Look up the cause, effect, and recovery information for a message either in OSS