Commit | Line | Data |
---|---|---|
e3758c96 C |
1 | .TH INTRO 1 |
2 | .UC 4 | |
3 | .SH NAME | |
4 | intro \- introduction to commands | |
5 | .SH DESCRIPTION | |
6 | This section describes publicly accessible commands | |
7 | in alphabetic order. | |
8 | Certain distinctions of purpose are made in the headings: | |
9 | .TP | |
10 | (1) | |
11 | Commands of general utility. | |
12 | .TP | |
13 | (1C) | |
14 | Commands for communication with other systems. | |
15 | .TP | |
16 | (1G) | |
17 | Commands used primarily for graphics and computer-aided design. | |
18 | .PP | |
19 | N.B.: Commands related to system maintenance, which appeared in | |
20 | section 1, distinguished by (1M), in previous versions of the manual | |
21 | have been moved to section 8, as they are of little interest to most | |
22 | users. | |
23 | .PP | |
24 | The word `VAX-11' at the foot of a page means that some or all | |
25 | of the description applies only to the implementation for the | |
26 | Digital Equipment Corporation VAX-11. | |
27 | Pages added or changed between the distribution of UNIX/32V and the | |
28 | Berkeley Distribution indicate `3rd Berkeley Distribution' or | |
29 | `4th Berkeley Distribution' at the lower left, as appropriate. | |
30 | .SH SEE ALSO | |
31 | Section (6) for computer games, section (8) for system maintenance | |
32 | commands. | |
33 | .PP | |
34 | .I How to get started, | |
35 | in the Introduction. | |
36 | .SH DIAGNOSTICS | |
37 | Upon termination each command returns two bytes of status, | |
38 | one supplied by the system giving the cause for | |
39 | termination, and (in the case of `normal' termination) | |
40 | one supplied by the program, | |
41 | see | |
42 | .I wait | |
43 | and | |
44 | .IR exit (2). | |
45 | The former byte is 0 for normal termination, the latter | |
46 | is customarily 0 for successful execution, nonzero | |
47 | to indicate troubles such as erroneous parameters, bad or inaccessible data, | |
48 | or other inability to cope with the task at hand. | |
49 | It is called variously `exit code', `exit status' or | |
50 | `return code', and is described only where special | |
51 | conventions are involved. |