Commit | Line | Data |
---|---|---|
95e2a96a KT |
1 | .TH INTRO 1 |
2 | .SH NAME | |
3 | intro \- introduction to commands | |
4 | .SH DESCRIPTION | |
5 | This section describes publicly accessible commands | |
6 | in alphabetic order. | |
7 | Certain distinctions of purpose are made in the headings: | |
8 | .TP | |
9 | (1) | |
10 | Commands of general utility. | |
11 | .TP | |
12 | (1C) | |
13 | Commands for communication with other systems. | |
14 | .TP | |
15 | (1G) | |
16 | Commands used primarily for graphics and computer-aided design. | |
17 | .TP | |
18 | (1M) | |
19 | Commands used primarily for system maintenance. | |
20 | .PP | |
21 | The word `local' at the foot of a page means that the | |
22 | command is not intended for general distribution. | |
23 | .SH SEE ALSO | |
24 | .SH DIAGNOSTICS | |
25 | Section (6) for computer games. | |
26 | .PP | |
27 | .I How to get started, | |
28 | in the Introduction. | |
29 | .SH DIAGNOSTICS | |
30 | Upon termination each command returns two bytes of status, | |
31 | one supplied by the system giving the cause for | |
32 | termination, and (in the case of `normal' termination) | |
33 | one supplied by the program, | |
34 | see | |
35 | .I wait | |
36 | and | |
37 | .IR exit (2). | |
38 | The former byte is 0 for normal termination, the latter | |
39 | is customarily 0 for successful execution, nonzero | |
40 | to indicate troubles such as erroneous parameters, bad or inaccessible data, | |
41 | or other inability to cope with the task at hand. | |
42 | It is called variously `exit code', `exit status' or | |
43 | `return code', and is described only where special | |
44 | conventions are involved. |