The following example procedure shows how to ensure that the Application Server man pages are available using the C shell.
Check your MANPATH environment variable to see if the correct path is already there.
env | grep MANPATH
If the correct path is not there, add the location of your Java ES 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.
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. You must also set the MANSECT variable.
On HP-UX, update the /etc/MANPATH file with the required MANPATH. For example, add this line to the /etc/MANPATH file:
/opt/sun/man |
On Linux, you might need to set the MANSECT environment variable.
Edit the MANSECT line in the /etc/man.config file. For example:
# and the MANSECT environment variablle is not set. MANSECT 1:8:2:3:4:5:6:7:9:tcl:n:l:p:o |
Change the second line to read this:
MANSECT 1:8:2:3:4:5:6:7:9:tcl:n:l:p:o:5:dsconf:5dpconf:5dssd:5dsat:5dsoc |
Verify that the man pages are accessible.
For example, the following command should display the asadmin man page for Application Server:
man asadmin |