INTRO(1M-SysV) RISC/os Reference Manual INTRO(1M-SysV)
NAME
intro - introduction to maintenance commands and application
programs
DESCRIPTION
This section describes, in alphabetical order, commands that
are used chiefly for system maintenance and administration
purposes. The commands in this section should be used along
with those listed in Section 1 of the User's Reference
Manual and Sections 2, 3, 4, and 5 of the Programmer's
Reference Manual. References of the form name(1), (2), (3),
(4) and (5) refer to entries in the above manuals. Refer-
ences of the form name(1M), name(7), or name(8) refer to
entries in this manual.
COMMAND SYNTAX
Unless otherwise noted, commands described in this section
accept options and other arguments according to the follow-
ing syntax:
name [option(s)] [cmdarg(s)]
where:
name The name of an executable file.
option - noargletter(s) or,
- argletter<>optarg
where <> is optional white space.
noargletter A single letter representing an option
without an argument.
argletter A single letter representing an option
requiring an argument.
optarg Argument (character string) satisfying
preceding argletter.
cmdarg Path name (or other command argument) not
beginning with - or, - by itself indicating
the standard input.
SEE ALSO
getopt(1) in the User's Reference Manual.
getopt(3C) in the Programmer's Reference Manual.
DIAGNOSTICS
Upon termination, each command returns two bytes of status,
one supplied by the system and giving the cause for termina-
tion, and (in the case of ``normal'' termination) one sup-
plied by the program (see wait(2) and exit(2)). The former
Printed 1/15/91 Page 1
INTRO(1M-SysV) RISC/os Reference Manual INTRO(1M-SysV)
byte is 0 for normal termination; the latter is customarily
0 for successful execution and non-zero to indicate troubles
such as erroneous parameters, bad or inaccessible data, or
other inability to cope with the task at hand. It is called
variously ``exit code'', ``exit status'', or ``return
code'', and is described only where special conventions are
involved.
ERRORS
Regrettably, not all commands adhere to the aforementioned
syntax.
Page 2 Printed 1/15/91