Open System Services Management and Operations Guide (G06.30+, H06.08+, J06.03+)

you can determine the following information for all servers administered through the OSS Monitor:
• The type of server (OSS name server, OSS message-queue server, and so on)
• The processor used by the primary server process
• The processor used by the backup server process
The following additional information is displayed when you specify the DETAIL option in the INFO
SERVER command:
• The user who created the server configuration, when it was created, the user who last modified
the configuration, and when it was last modified
• The automatic startup settings for the server (AUTORESTART, DESIREDSTATE, and
PERSISTENCECOUNT attributes)
• If the server is an OSS name server:
The size of the inode cache◦
◦ The size of the link cache
◦ The timeout value used for input or output with the SQL catalog server
NOTE: Beginning with the J06.15 and H06.26 RVUs, additional OSS SEEP-related attributes
for the OSS name server are listed. For details of the OSS SEEP-related attributes that are
displayed, see “INFO SERVER Command” (page 301).
• If the server is the OSS message-queue server:
The maximum number of bytes allowed in a message queue◦
◦ The maximum number of message queue IDs allowed at any time
◦ The maximum number of messages allowed on all message queues on a node
◦ The maximum size of a message in bytes
The information displayed is the configuration to be used the next time the server is started. The
currently running server process might be using different values.
Additional information about recent server errors is available using the DETAIL option of the OSS
Monitor SCF STATUS SERVER command.
For the OSS message-queue server, you can also obtain information about current usage by entering
the ipcs command from an OSS shell prompt. For more information about the ipcs command,
see the ipcs(1) reference page either online or in the Open System Services Shell and Utilities
Reference Manual.
Determining Usage and Configuration of Network Services Servers
To determine information about a running inetd, rshd, rexecd, or named process, use the ps
command. To check the most recent configuration information for inetd, use a text editor in the
environment in which the configuration file actually resides to view the content of the file.
To determine information about a running portmap process, use the RPCINFO command. Examples
of RPCINFO use can be found in relevant product manuals, such as the Open System Services
NFS Management and Operations Guide.
To check the most recent configuration for portmap, you need to know how the process was
started; the OSS shell show_define command or the TACL SHOW DEFINE command might be
useful if you know that DEFINEs were used when the process was started.
132 Managing Servers