Visit Our UNIX and Linux User Community

Linux and UNIX Man Pages

Test Your Knowledge in Computers #1008
Difficulty: Medium
A power series will converge for some values of the variable x and may diverge for others.
True or False?
Linux & Unix Commands - Search Man Pages

intro(1) [bsd man page]

INTRO(1)						      General Commands Manual							  INTRO(1)

NAME
intro - introduction to commands DESCRIPTION
This section describes publicly accessible commands in alphabetic order. Certain distinctions of purpose are made in the headings: (1) Commands of general utility. (1C) Commands for communication with other systems. (1G) Commands used primarily for graphics and computer-aided design. N.B.: Commands related to system maintenance used to appear in section 1 manual pages and were distinguished by (1M) at the top of the page. These manual pages now appear in section 8. SEE ALSO
Section (6) for computer games. How to get started, in the Introduction. DIAGNOSTICS
Upon termination each command returns two bytes of status, one supplied by the system giving the cause for termination, and (in the case of `normal' termination) one supplied by the program, see wait and exit(2). The former byte is 0 for normal termination, the latter is cus- tomarily 0 for successful execution, nonzero to indicate troubles such as erroneous parameters, bad or inaccessible data, or other inabil- ity 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. 7th Edition April 29, 1985 INTRO(1)

Check Out this Related Man Page

intro(1M)																 intro(1M)

NAME
intro - introduction to system maintenance commands and application programs DESCRIPTION
This section describes commands that are used chiefly for system maintenance and administration purposes. The commands in this section should be used in conjunction with other sections of this manual, as well as the HP-UX System Administration manuals for your system. Command Syntax Unless otherwise noted, commands described in this section accept options and other arguments according to the following syntax: name [ option ( s )] [ cmd_arg ( s )] where the elements are defined as follows: name Name of an executable file. option One or more options can appear on a command line. Each takes one of the following forms: A single letter representing an option without an argument. Two or more single-letter options combined into a single command-line argument. A single-letter option followed by a required argument where: arg_letter is the single letter representing an option that requires an argument, opt_arg is an argument (character string) satisfying the preceding arg_letter, <> represents optional white space. cmd_arg Path name (or other command argument) not beginning with or by itself indicating the standard input. If two or more cmd_args appear, they must be separated by white space. RETURN STATUS
Upon termination, each command returns two bytes of status, one supplied by the system giving the cause for termination, and (in the case of ``normal'' termination) one supplied by the program (for descriptions, see wait(2) and exit(2)). The system-supplied byte is 0 for nor- mal termination. The byte provided by the program is customarily 0 for successful execution and non-zero to indicate errors or failure such as incorrect parameters in the command line, or bad or inaccessible data. Values returned are usually called variously ``exit code'', ``exit status'', or ``return code'', and are described only where special conventions are involved. WARNINGS
Some commands produce unexpected results when processing files containing null characters. These commands often treat text input lines as strings and therefore become confused upon encountering a null character (the string terminator) within a line. SEE ALSO
getopt(1), exit(2), wait(2), getopt(3C), hier(5), introduction(9). Web access to HP-UX documentation at intro(1M)

Featured Tech Videos