Page 1248 SECTIONS Sections are started with .SH followed by the heading name. If the name contains spaces and appears on the same line as .SH, then place the heading in double quotes. Traditional headings include NAME, SYNOPSIS, DESCRIPTION, OPTIONS, FILES, SEE ALSO, DIAGNOSTICS, BUGS, and AUTHOR. The only required heading is NAME, which should be followed on the next line by a one line description of the program: .SH NAME chess \- the game of chess It is extremely important that this format is followed and that there is a backslash before the single dash that follows the command name. This syntax is used by the makewhatis(8) program to create a database of short command descriptions for the whatis(1) and apropos(1) commands. OTHER MACROS Other macros include the following:
FILES /usr/local/lib/groff/tmac/tmac.an /usr/man/whatis SEE ALSO groff(1), man(1), whatis(1), apropos(1), makewhatis(8) Linux, 25 July 1993 signalsignalList of available signals. DESCRIPTION Linux supports the signals listed in this section. Several signal numbers are architecture dependent. First are the signals described in POSIX.1: abort(3) alarm(1) Next various other signals. (Here, _ denotes that a signal is absent; there, where three values are given, the first one is usually valid for alpha and sparc, the middle one for i386 and ppc, the last one for mips. Signal 29 is SIGINFO/SIGPWR on an alpha but SIGLOST on a sparc.) Page 1249 The letters in the Action column have the following meanings:
CONFORMING TO POSIX.1 BUGS SIGIO and SIGLOST have the same value. The latter is commented out in the kernel source, but the build process of some software still thinks that Signal 29 is SIGLOST. SEE ALSO kill(1), kill(2), setitimer(2) Linux 1.3.88, 14 April 1996 suffixessuffixesList of file suffixes. DESCRIPTION It is customary to indicate the contents of a file with the file suffix, which consists of a period followed by one or more letters. Many standard utilities, such as compilers, use this to recognize the type of file they are dealing with. The make(1) utility is driven by rules based on file suffixes. Following is a list of suffixes that are likely to be found on a Linux system:
continues |