28
Dec
Comcast web hosting - arc h”). Section Numbers and Man You might
arc h”). Section Numbers and Man You might find cases where the man page you want has the same name as a man page in some other section of the manual, especially as you add additional software to your OpenBSD machines. In those cases, specifying the section number is the only way to get the exact page you want. Without giving a section number, you’ll get the man page of that name with the lowest section number. You can specify a section number before the name of the command, i.e.: # man 8 ping While this example is rather trivial (a “ping” man page only appears in one section of the manual), we’ll look in some other cases where it isn’t. Man Page Contents Man pages have a variety of section headers. While just about any subsection can appear in a man page, several are standard. (See mdoc(7) for a partial list of standard section names, as well as other man page standards.) Like book authors, man page authors try to arrange their content in a manner that makes sense for the program they’re describing. Still, you will see some standard headings. . NAME tells you the names of a program or utility. Some programs have multiple names for example, the vi(1) text editor is also available as view(1) or ex(1). The man page lists all of these names. . SYNOPSIS lists the possible command-line options and their arguments, or how a library call is accessed. Frequently, you’ll find that this header is enough to spark your memory and remind you of a flag you’ve used before that caused the program to behave appropriately. . DESCRIPTION contains a brief synopsis of the program or feature. The contents of this section vary depending on the topic, as programs, files, and interfaces all have very different documentation requirements. . OPTIONS describes a program’s command-line options and their effects. . BUGS describes known failure conditions, weird behavior, and how to make the program fail in general. This is a great time-saver. Many times I’ve had a problem with a command only to find that behavior, and sometimes a workaround, listed in the BUGS section. Honesty is a wonderful thing in computing products. . SEE ALSO is traditionally the last section in a man page. OpenBSD is an interrelated whole; every command has ties to other commands. In an ideal world you would read every man page and be able to hold an integrated image of the system in your head. Because most of us cannot do that, this section provides directions to related man pages. You now know what you need to navigate the integrated help system. Now let’s look at some information resources elsewhere than your computer. Man Pages on the Web The manual pages are also available on www.OpenBSD.org and its mirrors. While your system has only the man pages for your release and architecture of OpenBSD, the manual available on the website includes all previous versions of OpenBSD and all architectures. If you want to see differences in the boot process between i386 and Alpha platforms, you can easily compare the manual pages on the website. Similarly, you can see which release certain commands were first documented in and how those commands have changed over time. Page 25
Note: If you are looking for cheapest and affordable webspace to host and run your servlet application check Astra j2ee hosting services