Solaris man pages (manual pages) are well written, consistent, complete, and generally a great source of information. Here are a few tips to help you get the most out of them. Of course this applies to all Solaris derivatives, including proper Solaris, OpenSolaris and other Open Solaris distributions like Solaris Express, Belenix and Nexenta. It even applies to other Unix flavors like BSD and AIX, and Unix derivatives like Linux.
The simplest (and most obvious) way to use the manual pages are to enter "man command" and then read the entire page.
My first hint however is to change the "PAGER" environment variable. I suggest you set it like this in your .profile file:
(or for csh and its family members, use setenv PAGER "less -iMsq")
The reasons for this are
a) "less" supports more useful options than does "more". In particular, it supports highlighting, as well as all of the below!
b) The "-i" causes less to ignore case in searches. A definite advantage because you can simply enter /user and it will find the string "user" even when capitalized for use at the start of a sentence.
c) The -M causes "less" to show a more verbose status at the bottom of the screen.
d) -q ... Stop irritating me.
e) -s to "squeeze" blank lines (because otherwise less will "format" pages with blank spaces, as if it is a printed page)
f) You can return to the first line (top) of the page by taping "1" followed by "G"
g) less is more.
The PAGER environment variable is automatically used by the man command, so you can now test it and will find that you can scroll up and down in man pages. To find a word in the man page, tap the forward-slash / followed by the string to search for, and the word wherever it is found will be highlighted in inverse text.
Note: less does have some limitations over more, but these do not apply to viewing man pages. For the curious, the limitation is in the handling of control characters in the input file. In particular, more does a better job of displaying "captured" sessions recorded from a system console or from a shell using the "script" command. Regardless, I solve these by reading capture files using cat -nvet | less -iMq (Note - I like seeing line numbers)
Second Hint: Generate the Manual Pages keyword index database (The so-called windex or apropos information). To do this, you need to run the following command once.
This will run for a while as it generates and stores the man page keyword index for future use.
Once it completes, the man command's -k option and the "whatis" command will work. This allows you to find what you need much easier. For example to find all man pages for tools, commands and drivers related to Wifi and Wireless networking, you can use
Third hint: Some man pages are not automatically searched or found. In older (proper) Solaris releases, the man command has got a "default list" of locations where to find man pages. In Recent Open Solaris releases, man constructs a list of locations to search. The man manual page states:
Search Path Before searching for a given name, man constructs a list of candidate directories and sections. man searches for name in the directories specified by the MANPATH environment vari- able. In the absence of MANPATH, man constructs its search path based upon the PATH environment variable, primarily by sub- stituting man for the last component of the PATH element. Special provisions are added to account for unique charac- teristics of directories such as /sbin, /usr/ucb, /usr/xpg4/bin, and others. If the file argument contains a / character, the dirname portion of the argument is used in place of PATH elements to construct the search path.
Note: The (currently apparently undocumented) -p option to man will show the effective man search path.
As implied, you can set in MANPATH a list of directories containing man pages you use regularly. It is also possible to overide the man search path using the man command's -M option. This is particularly true for packages that install under /usr/local, /opt/SUNW...., etc. So to view the man page for "explorer" you would run:
(Assuming you have SUNWexplorer installed)
Finally, it helps to understand the structure of a man page. The individual manual pages are divided up into a common set of sections, and knowing them you will often skip straight to a specific (sub)section in the page when looking for specific information.
Some of these subsections are optional, but the names used are consistent. Here is a quick summary of some important sections.
|NAME||What this page is about. This is the "whatis" information.|
|SYNOPSIS||The summary, eg how to use a command.|
|DESCRIPTION||A more complete description of what this component is.|
|OPTIONS, OPERANDS and USAGE||These section details how a command is used, eg what command-line options are available for a specific command.|
|ENVIRONMENT VARIABLES||As the name suggests, this section details Environment variables which affects the behavior of the command.|
|EXIT STATUS||As the name implies, it explains the possible exit status values. Useful to know that the section exists though.|
|FILES||A list of files which are relevant to the command or subsystem. In particular here you will find out where a program keeps its configuration files. For a good example, see man dumpadm.|
|EXAMPLES||Often a great place to skip to when a manual page is complicated.|
|ATTRIBUTES||An often overlooked section, it explains the status of the item. For commands it tells you which packages the files are in. This section of man pages are fully explained in the "attributes" manual page.|
|SEE ALSO||One of the most useful parts of man pages, this gives you hints about other pages which are related to the same topic.|
|NOTES||Various Additional notes.|
Other sections, such as SECURITY, ERRORS, SUBCOMMANDS, etc exists in some man pages, but the above are probably the most useful sections.
The entire collection of man pages are divided up into manual sections, such as Section 1 - User Commands, Section 1M - Maintenance commands for sys-admins, Section 3C, the C programming reference information and section 7 - information about device drivers. This is not hugely important, except that you need to understand that some pages occur in more than one section. For example "read" or "signal" By default, man will display the first manual page which matches the file name. If you want to see one of the other pages you need to specify the specific manual section explicitly.
$ man -f signal
We can see that file "signal" has got manual entries in sections 3c (C programming reference), 3ucb (UCB/Posix version), and 3head (the Headers section)
Simply entering ||man signal|| will show the man page from "3C". To see the man page in the "3head" section, enter either
I often end up using the second form simply because after viewing a man page I often see that there is another related man page from the SEE ALSO section. I then exit the man page, recall the previous command, and append .section to the command line, which is to say that it is just a matter of convenience.
One last tip: There are online versions of the manual pages at http://docs.sun.com.
You don't need to learn every command and every option by heart. Knowing that you have manual pages, and that you can look up the information you need quickly by looking at related commands from SEE ALSO, and from the keyword index using man -k, and then being able to quickly search through man pages for the right section or keyword absolutely WILL make you a clever, more efficient and over all better sysadmin!