Verifying the MANPATH

If your components have man pages, you will need to verify that your MANPATH environmental variable is set correctly. After installation, the man pages for the Communications Suite components are located in default directories. In some cases, the correct location for the component man pages is already set in your MANPATH environment variable. If the location of your man pages is not present, add this location to your MANPATH environment variable.

The following table indicates the default locations for the man pages of the Communications Suite components. If a component is not listed, the component does not have man pages.

To Update Your MANPATH Variable

The following example procedure shows how to ensure that the Application Server man pages are available using the C shell.

1. Check your MANPATH environment variable to see if the correct path is already there.

   env | grep MANPATH

2. If the correct path is not there, add the location of your Communications Suite component man pages to your MANPATH environment variable.

   • On Solaris OS, the following example command sets your MANPATH environment variable for the session:

     setenv MANPATH {$MANPATH}:/usr/dt/man:/usr/man:/opt/SUNWappserver/share/man

     To configure this environment variable to apply each time you log in, add the setenv command contents to your .login or .cshrc file.

   • On Linux, update the /etc/man.config file with the required MANPATH. For example, add this line to the /etc/man.config file:

     MANPATH /opt/sun/man

     The new man pages will be fully accessible, regardless of path.

     ---

     Note –

     For Linux, if users have MANPATH settings in their own shells, the procedure for Solaris OS should be used. This allows their personal settings to override the /etc/man.config file.

     ---

3. Verify that the man pages are accessible.

   For example, the following command should display the asadmin man page for Application Server:

   man asadmin