01.01.2013 Views

AT&T UNIX™PC Unix System V Users Manual - tenox

AT&T UNIX™PC Unix System V Users Manual - tenox

AT&T UNIX™PC Unix System V Users Manual - tenox

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

INTRO ( 1) INTRO ( l )<br />

NAME<br />

intro - introduction to commands and application programs<br />

DESCRIPTION<br />

This section describes, in alphabetical order, publicly-accessible<br />

commands. Certain distinctions of purpose are made in the head­<br />

ings:<br />

(1)<br />

(1C)<br />

(1G)<br />

Commands of general utility.<br />

Commands for communication with other systems.<br />

Commands used primarily for graphics and computeraided<br />

design.<br />

COMMAND SYNTAX<br />

Unless otherwise noted, commands described in this section accept<br />

options and other arguments according to the following syntax:<br />

name [option( 8 )] [ cmdarg( 8 )]<br />

where:<br />

name<br />

option<br />

noargletter<br />

argletter<br />

optarg<br />

cmdarg<br />

The name of an executable file.<br />

- noargletter( 8 ) or,<br />

- argletter < > optarg<br />

where < > is optional white space.<br />

A single Jetter representing an option without an<br />

argument.<br />

A single letter representing an option requiring an<br />

argument.<br />

Argument (character string) satisfying preceding<br />

argletter.<br />

Path name (or other command argument) not<br />

beginning with - or, - by itself indicating the standard<br />

input.<br />

SEE ALSO<br />

getopt(1), getopt(3C).<br />

DIAGNOSTICS<br />

Upon termination, each command returns two bytes of status, one<br />

supplied by the system and giving the cause for termination, and<br />

(in the case of "normal" termination) one supplied by the program<br />

(see wait(2) and exit(2)). The former byte is 0 for normal termination;<br />

the latter is customarily 0 for successful execution and<br />

non-zero to indicate troubles such as erroneous parameters, bad or<br />

inaccessible data, or other inability to cope with the task at hand.<br />

It is called variously "exit code", "exit status", or "return code",<br />

and is described only where special conventions are involved.<br />

BUGS<br />

Regretfully, many commands do not adhere to the aforementioned<br />

syntax.<br />

- 1 -

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!