Digital PDFs

AD-PCOWA-T1

June 1990

432 pages

Original

18MB

view download

OCR Version

17MB

view download

Document:	ULTRIX Reference Pages Section 1: Commands M - Z
Order Number:	AD-PCOWA-T1
Revision:	0
Pages:	432
Original Filename:

OCR Text

ULTRIX

Reference Pages Section 1: Commands M - Z

Order Number: AD-PCOWA-T1
June 1990

Product Version:

ULTRIX Version 4.0 or higher

This manual describes commands from M to Z that are available to all ULTRIX users
for
both RISC and VAX platforms.

digital equipment corporation

maynard, massachusetts

Restricted Rights: Use, duplication, or disclosure by the U.S. Government is subject to restrictions as set forth in
subparagraph (c) (1) (ii) of the Rights in Technical Data and Computer Software clause of DFARS 252.227-7013.
© Digital Equipment Corporation 1984, 1986, 1988, 1990
All rights reserved.

Portions of the information herein are derived from copyrighted material as permitted under license agreements with
AT&T and the Regents of the University of California. © AT&T 1979, 1984. All Rights Reserved.

Portions of the information herein are derived from copyrighted material as permitted under a license agreement with
Sun MicroSystems, Inc. © Sun MicroSystems, Inc, 1985. All Rights Reserved.

Portions of this document © Massachusetts Institute of Technology, Cambridge, Massachusetts, 1984, 1985, 1986,
1988.

The information in this document is subject to change without notice and should not be construed as a commitment
by Digital Equipment Corporation. Digital Equipment Corporation assumes no responsibility for any errors that may
appear in this document.

The software described in this document is furnished under a license and may be used or copied only in accordance
with the terms of such license.

No responsibility is assumed for the use or reliability of software on equipment that is not supplied by Digital or its
affiliated companies.

The following are trademarks of Digital Equipment Corporation:

Engnan
CDA
DDIF
DDIS

DEC

DECnet
DECstation

DECUS

ULTRIX Worksystem Software

DTIF
MASSBUS
MicroVAX

VAX
VAXstation
VMS

DECwindows

Q-bus

ULTRIX
ULTRIX Mail Connection

UNIBUS

VMS/ULTRIX Connection
VT
XUI

Ethernet is a registered trademark of Xerox Corporation.

Network File System and NFS are trademarks of Sun Microsystems, Inc.

POSIX is a registered trademark of the Institute of Electrical and Electronics Engineers.
System V is a registered trademark of AT&T.
Tektronix is a trademark of Tektronix, Inc.

Teletype is a registered trademark of AT&T in the USA and other countries.
UNIX is a registered trademark of AT&T in the USA and other countries.

About Reference Pages

The ULTRIX Reference Pages describe commands, system calls, routines,
file
formats, and special files for RISC and VAX platforms.

Sections
The reference pages are divided into eight sections according to topic.

Within each
section, the reference pages are organized alphabetically by title, except
Section 3,
which is divided into subsections. Each section and most subsectio
ns have an
introductory reference page called int ro that describes the organizat
ion and
anything unique to that section.
Some reference pages carry a one- to three-letter suffix after the section
number, for
example, scan(lmh). The suffix indicates that there is a ““family’’
of reference
pages for that utility or feature. The Section 3 subsections all use
suffixes and other
sections may also have suffixes.

Following are the sections that make up the ULTRIX Reference Pages.

Section 1: Commands
This section describes commands that are available to all ULTRIX users.
Section 1 is
split between two binders. The first binder contains reference pages
for titles that fall
between A and L. The second binder contains reference pages for titles
that fall
between M and Z.

Section 2: System Calls
This section defines system calls (entries into the ULTRIX kernel) that are
used by
all programmers. The introduction to Section 2, intro(2), lists error numbers
with
brief descriptions of their meanings. The introduction also defines many of
the terms
used in this section.

Section 3: Routines
This section describes the routines available in ULTRIX libraries. Routines are
sometimes referred to as subroutines or functions.

Section 4: Special Files
This section describes special files, related device driver functions, databases, and

network support.

Section 5: File Formats

This section describes the format of system files and how the files are used. The files
described include assembler and link editor output, system accounting, and file
system formats.

Section 6: Games

The reference pages in this section describe the games that are available in the
unsupported software subset. The reference pages for games are in the document

Reference Pages for Unsupported Software.

Section 7: Macro Packages and Conventions
This section contains miscellaneous information, including ASCII character codes,
mail addressing formats, text formatting macros, and a description of the root file
system.

Section 8: Maintenance

This section describes commands for system operation and maintenance.

Platform Labels
The ULTRIX Reference Pages contain entries for both RISC and VAX platforms.
Pages that have no platform label beside the title apply to both platforms. Reference

pages that apply only to RISC platforms have a “RISC’’ label beside the title and the
VAX-only reference pages that apply only to VAX platforms are likewise labeled
with ““VAX.”’ If each platform has the same command, system call, routine, file
format, or special file, but functions differently on the different platforms, both
reference pages are included, with the RISC page first.

Reference Page Format
Each reference page follows the same general format. Common to all reference pages
is a title consisting of the name of a command or a descriptive title, followed by a
section number; for example, date(1). This title is used throughout the
documentation set.

The headings in each reference page provide specific information. The standard
headings are:

Name
Syntax

Provides the name of the entry and gives a short description.
Describes the command syntax or the routine definition. Section 5

Description

Provides a detailed description of the entry’s features, usage, and

Options

Describes the command-line options.

reference pages do not use the Syntax heading.
syntax variations.

Restrictions

Describes limitations or restrictions on the use of a command or

Examples

Provides examples of how a command or routine is used.

iv About Reference Pages

routine.

Return Values

Describes the values returned by a system call or routine. Used in
Sections 2 and 3 only.

Diagnostics

Describes diagnostic and error messages that can appear.

Files

Lists related files that are either a part of the command or used
during execution.

Environment

Describes the operation of the system call or routine when
compiled in the POSIX and SYSTEM YV environments. If the
environment has no effect on the operation, this heading is not
used. Used in Sections 2 and 3 only.

See Also

Lists related reference pages and documents in the ULTRIX
documentation set.

Conventions
The following documentation conventions are used in the reference pages.

The default user prompt is your system name followed by a right

angle bracket. In this manual, a percent sign (%) is used to
represent this prompt.

#
user

A number sign is the default superuser prompt.
input

This bold typeface is used in interactive examples to indicate
typed user input.

system output This typeface is used in text to indicate the exact name of a
command, routine, partition, pathname, directory, or file. This

typeface is also used in interactive examples to indicate system
output and in code examples and other screen displays.
UPPERCASE
lowercase

The ULTRIX system differentiates between lowercase and
uppercase characters. Literal strings that appear in text,

examples, syntax descriptions, and function definitions must be
typed exactly as shown.
rlogin

This typeface is used for command names in the Syntax portion

of the reference page to indicate that the command is entered
exactly as shown. Options for commands are shown in bold
wherever they appear.

filename

In examples, syntax descriptions, and routine definitions, italics

are used to indicate variable values. In text, italics are used to
give references to other documents.

[]

In syntax descriptions and routine definitions, brackets indicate
items that are optional.

{1}

In syntax descriptions and routine definitions, braces enclose lists

from which one item must be chosen. Vertical bars are used to

separate items.

About Reference Pages v

« o .

In syntax descriptions and routine definitions, a horizontal ellipsis
indicates that the preceding item can be repeated one or more
times.

)

cat(l)

A vertical ellipsis indicates that a portion of an example that
would normally be present is not shown.

Cross-references to the ULTRIX Reference Pages include the

appropriate section number in parentheses. For example, a
reference to cat(1) indicates that you can find the material on the
cat command in Section 1 of the reference pages.

Online Reference Pages
The ULTRIX reference pages are available online if installed by your system
administrator. The man command is used to display the reference pages as follows:
To display the 1s(1) reference page:
% man ls

To display the passwd(1) reference page:
% man passwd

To display the passwd(5) reference page:
% man 5 passwd

To display the Name lines of all reference pages that contain the word ‘‘passwd’’:
% man -k passwd

To display the introductory reference page for the family of 3xti reference pages:
% man 3xti intro

Users on ULTRIX workstations can display the reference pages using the
unsupported xman utility if installed. See the xman(1X) reference page for details.

Reference Pages for Unsupported Software
The reference pages for the optionally installed, unsupported ULTRIX software are in
the document Reference Pages for Unsupported Software.

vi About Reference Pages

m4(1)

Name
m4 — macro processor

Syntax
m4 [options] [files]

Description
The m4 macro processor is intended as a front end for Ratfor, C, and other languages.

Each of the argument files is processed in order; if there are no arguments, or if an
argument is hypen (-), the standard input is read. The processed text is written on the
standard output.

Options
The options and their effects are as follows:

Operate interactively. Interrupts are ignored and the output is

—-e

unbuffered.

-s

Enable line sync output for the C preprocessor (#line . .)

-Bint

Change the size of the push-back and argument collection buffers

—Hint

Change the size of the symbol table hash array from the default of

from the default of 4,096.

199. The size should be prime.

Change the size of the call stack from the default of 100 slots.

=Sint

Macros take three slots, and non-macro arguments take one.

Change the size of the token buffer from the default of 512 bytes.

—Tint

To be effective, these flags must appear before any file names and before any —-D or

-U flags:

~Dname[=val]

Defines name to val or to null in val’s absence.

-Uname

undefines name.

Macro calls have the following form:
name (argl,arg2,

argn)

The left parenthesis ( ( ) must immediately follow the name of the macro. If a
defined macro name is not followed by a left parenthesis, it is deemed to have no
arguments.

Leading unquoted blanks, tabs, and new lines are ignored while collecting arguments.
Potential macro names consist of alphabetic letters, digits, and underscore (_), where
the first character is not a digit.

Left and right single quotes (" *) are used to quote strings. The value of a quoted
string is the string stripped of the quotes.

Commands 1-389

m4(1)
When a macro name is recognized, its arguments are collected by searching for a

matching right parenthesis. Macro evaluation proceeds normally during the
collection of the arguments, and any commas or right parentheses which happen to

turn up within the value of a nested call are as effective as those in the original input
text. After argument collection, the value of the macro is pushed back onto the input
stream and rescanned.

The m4 makes available the following built-in macros. They may be redefined, but
once this is done the original meaning is lost. Their values are null unless otherwise
stated.

define

The second argument is installed as the value of the macro
whose name is the first argument. Each occurrence of $# in
the replacement text, where ~ is a digit, is replaced by the
n-th argument. Argument O is the name of the macro;
missing arguments are replaced by the null string. $# is
replaced by the number of arguments; $* is replaced by a list
of all the arguments separated by commas; $@ is like $*,
but each argument is quoted (with the current quotes).

undefine

removes the definition of the macro named in its argument.

defn

returns the quoted definition of its argument(s). It is useful
for renaming macros, especially built-ins.

pushdef

like define, but saves any previous definition.

popdef

removes current definition of its argument(s), exposing the
previous one, if any.

ifdef

If the first argument is defined, the value is the second
argument, otherwise the third. If there is no third argument,
the value is null. The word unix is predefined on UNIX
versions of m4 .

changequote

Change quote characters to the first and second arguments.
The changequote without arguments restores the original
values (that is, " ).

changecom

change left and right comment markers from the default #
and new-line. With no arguments, the comment mechanism
is effectively disabled. With one argument, the left marker

becomes the argument and the right marker becomes newline. With two arguments, both markers are affected.
Comment markers may be up to five characters long.
divert

The m4 maintains 10 output streams, numbered 0-9. The
final output is the concatenation of the streams in numerical
order; initially stream O is the current stream. The divert
macro changes the current output stream to its (digit-string)
argument. Output diverted to a stream other than 0 through

9 is discarded.
undivert

causes immediate output of text from diversions named as
arguments, or all diversions if no argument. Text may be

undiverted into another diversion. Undiverting discards the
diverted text.

1-390 Commands

m4(1)
divhum

returns the value of the current output stream.

dnl

reads and discards characters up to and including the next

ifelse

has three or more arguments. If the first argument is the
same string as the second, then the value is the third
argument. If not, and if there are more than four arguments,
the process is repeated with arguments 4, 5, 6 and 7.
Otherwise, the value is either the fourth string, or, if it is not

new line.

present, null.
incr

returns the value of its argument incremented by 1. The
value of the argument is calculated by interpreting an initial
digit-string as a decimal number.

decr

returns the value of its argument decremented by 1.

eval

evaluates its argument as an arithmetic expression, using
32-bit arithmetic. Operators include +, —, *, /, %, A

(exponentiation), bitwise &, | , A, and ~; relationals;

parentheses. Octal and hex numbers may be specified as in
C. The second argument specifies the radix for the result;
the default is 10. The third argument may be used to specify
the minimum number of digits in the result.

len

returns the number of characters in its argument.

index

returns the position in its first argument where the second
argument begins (zero origin), or -1 if the second argument
does not occur.

substr

returns a substring of its first argument. The second
argument is a zero origin number selecting the first
character; the third argument indicates the length of the
substring. A missing third argument is taken to be large
enough to extend to the end of the first string.

shift

is an unimplemented macro. Using shift generates an error
message.

translit

transliterates the characters in its first argument from the set
given by the second argument to the set given by the third.
No abbreviations are permitted.

include

returns the contents of the file named in the argument.

sinclude

is identical to include, except that it says nothing if the file is

syscmd

executes the UNIX command given in the first argument.

sysval

is the return code from the last call to syscmd.

maketemp
mdexit

inaccessible.

No value is returned.

fills in a string of XXXXX in its argument with the current
process id.

causes immediate exit from m4. Argument 1, if given, is the
exit code; the default is O.

Commands 1-391

m4(1)
m4wrap

argument 1 will be pushed back at final EOF. For example:
médwrap (‘cleanup()’)

errprint

prints its argument on the diagnostic output file.

dumpdef

prints current names and definitions, for the named items, or

for all if no arguments are given.
traceon

with no arguments, turns on tracing for all macros (including
built-ins). Otherwise, turns on tracing for named macros.

traceoff

turns off trace globally and for any macros specified.
Macros specifically traced by traceon can be untraced only
by specific calls to traceoff.

See Also
"The M4 Macro Processor," ULTRIX Supplementary Documents Vol. II:Programmer

1-392 Commands

machine (1)

Name
machine — return architecture type of machine

Syntax
machine

Description
The machine command prints on the standard output the architecture of the
machine. Legal values are either mips or vax depending upon your hardware. The
machine command is used within shell procedures to tailor the results to a specific
architecture.

The exit value of machine is always zero.

Commands 1-393

mail (1)

Name
mail — send or read mail

Syntax
mail [-v] [—i] [-n] [-e] [-s subject] [ user...]

mail [-v] [] [-n] —f [ name
]

mail [-v] [-i] [-n] —u user
mail nodename::username (If DECnet is installed.)

Description
The mail utility is an intelligent mail processing system which has a command

syntax similar to ed. However, in mail lines are replaced by messages.

If DECnet is installed on your system, you can also send and receive mail from other
DECnet users. See mailaddr(7) for information on DECnet addressing.

Sending mail. To send a message to one or more persons, type mail and the names
of the people receiving your mail. Press the RETURN key. Note that if you use
other arguments, the names of the recipients should always be the last element on the
command line. For example,
mail

-v -s

"mail message"

users

If you do not specify a subject on the command line, you are prompted for a subject.
After entering a subject, and pressing the RETURN key, type your message. To send
the message, type a period (.) or CTRL D at the beginning of a new line.
You can use tilde (~) escape sequences to perform special functions when composing
mail messages. See the list of options for more on tilde escape sequences.

Reading mail. In normal usage mail is given no arguments and checks your mail
out of the mail directory. Then it prints out a one line header of each message there.
The current message is initially the first message and is numbered 1. It can be
displayed using the print command.
The —e option causes mail not to be printed. Instead, an exit value is returned. For

the exit status, see RETURN VALUES. You can move among the messages by
typing a plus sign (+) followed by a number to move forward that many messages, or
a minus sign (-) followed by a number to move backward that many messages.
Disposing of mail. After reading a message you can delete (d) it or reply (r) to it.
Deleted messages can be undeleted, however, in one of two ways: you can use the
undelete (u) command and the number of the message, or you can end the mail

session with the exit (x) command. Note that if you end a session with the quit (q)
command, you cannot retrieve deleted messages.

Specifying messages. Commands such as print and delete can be given a list of
message numbers as arguments. Thus, the command
delete

deletes messages 1 and 2, while the command
delete

1-5

deletes messages 1 through 5. The asterisk (*) addresses all messages, and the dollar

sign ($) addresses the last message. For example, the top command, which prints

1-394 Commands

mail (1)
the first few lines of a message, can be used in the following manner to print the first
few lines of all messages:
top *

Replying to or originating mail. Use the reply command to respond to a message.
Ending a mail processing session. End a mail session with the quit (q)

command. Unless they were deleted, messages that you have read go to your mbox
file. Unread messages go back to the mail directory. The —f option causes mail to
read in the contents of your mbox (or the specified file) for processing. When you
quit, the mail utility writes undeleted messages back to this file. The —u flag is a
short way of specifying: mail -f /usr/spool/mail/user.

Personal and systemwide distribution lists. You can create a personal distribution
list that directs mail to a group of people. Such lists can be defined by placing a line
similar to the following in the .mailrc file in your home directory:
alias cohorts bill ozalp jkf mark kridlelucbcory

Cohorts is the name of the distribution list that consists of the following users: bill,
ozalp, jkf, mark, and kridle@ucbcory. A list of current aliases can be displayed with

the alias (a) command inmail.

System wide distribution lists can be created by editing /usr/lib/aliases.
The syntax of system wide lists differs from that of personally defined aliases.

Personal aliases are expanded in mail you send. When a recipient on a personally
defined mailing list uses the reply (r) option, the entire mailing list receives the
response automatically. System wide aliases are not expanded when the mail is sent,
but any reply returned to the machine will have the system-wide alias expanded as all
mail goes through sendmail.

Forwarding is also a form of aliasing. A .forward file can be set up in a user’s
home directory. Mail for that user is then redirected to the list of addresses in the
.forward file. See aliases(5) and sendmail(8) for more information.

Network mail (ARPA, UUCP, Berknet, DECnet) See mailaddr(7) for a description
of network addresses.

Options
—e
-f

Causes mail not to be printed. Instead, an exit value is returned.
Causes mail to read in the contents of your mbox file (or another file you

specify) for processing.

—i

Causes tty interrupt signals to be ignored. This is useful when using mail

-n

Inhibits the reading of /usr/lib/Mail.rc.

Specifies a subject on the command line. Note that only the first argument
after the —s flag is used as a subject and that you must enclose subjects

on noisy phone lines.

containing spaces in quotes.

-u

Specifies a short hand for expressing the following:
mail -f /usr/spool/mail/user

Commands 1-395

mail (1)
-V

Prints the mail message. The details of delivery are displayed on the
user’s terminal.

The following options can be set in the .mailrc file to alter the behavior of the mail
command.

Each command is typed on a line by itself and may take arguments following the
command word and the command abbreviation. For commands that take message
lists as arguments, if no message list is given, then the next message forward which
satisfies the command’s requirements is used. If there are no messages forward of
the current message, the search proceeds backwards. If there are no good messages
at all, mail cancels the command, displaying the message: No applicable messages.
-

Prints out the previous message. If given a numeric argument n, prints

Prints a brief summary of commands.

n-th previous message.

Executes the ULTRIX shell command which follows.

alias (a)

Prints out all currently-defined aliases, if given without arguments.

With one argument, prints out that alias. With more than one
argument, creates a new or changes an old alias. These aliases are in
effect for the current mail session only.

alternates (alt)

Informs mail that you have several valid addresses. The
alternates command is useful if you have accounts on more than
one machine. When you reply to messages, mail does not send a
copy of the message to any of the addresses listed on the alternates
list. If the alternates command is given with no argument, the
current set of alternate names is displayed.

chdir (ch)

Changes the user’s working directory to that specified. If no directory
is given, then the chdir command changes to the user’s login
directory.

copy (co)

Takes a message list and file name and appends each message to the

delete (d)

Takes a list of messages as argument and marks them all as deleted.
Deleted messages are not saved in mbox, nor are they available for

end of the file. The copy command functions in the same way as the
save command, except that it does not mark the messages that you
copy for deletion when you quit.

most other commands.

dp (or dt)

Deletes the current message and prints the next message. If there is no
next message, mail returns a message: at EOF.

edit (e)

Takes a list of messages and points the text editor at each one in turn.
On return from the editor, the message is read back in.

exit (ex or X) Returns to the Shell without modifying the user’s system mailbox,
mbox file, or edit file in —f.

file (fi)

1-396 Commands

Switches to a new mail file or folder. If no arguments are given, it
tells you which file you are currently reading. If you give it an
argument, it writes out changes (such as deletions) you have made in
the current file and reads in the new file. Some special conventions are

mail (1)

recognized for the name. A pound sign (#) indicates the previous file,
a percent sign (%) indicates your systemb mailbox, %user indicates
the user’s system mailbox, an ampersand (&) indicates your ~/mbox
file, and +folder indicates a file in your folder directory.

folders

List the names of the folders in your folder directory.

folder (fo)

Switches to a new mail file or folder. The folder command
functions in the same way as the £ile command.

from (f)

Takes a list of messages and prints their message headers in the order
that they appear in the mail directory, not in the order given in the list.

headers (h)

Lists the current range of headers, which is an 18 message group. If a
plus sign (+) is given as an argument, then the next message group is
printed. If a minus sign (-) is given as an argument, the previous
message group is printed.

help

Prints a brief summary of commands. Synonymous with ?.

hold (ho, also preserve)

Takes a message list and marks each message in it to be saved in the
user’s system mailbox instead of in mbox. The hold command does
not override the delete command.

ignore

Adds the list of header fields named to the ignored list. Header fields
in the ignore list are not printed on your terminal when you print a
message. This command is frequently used to suppress certain
machine-generated header fields. The type and print commands
are used to print a message in its entirety, including ignored fields. If
ignore is executed with no arguments, it lists the current set of
ignored fields.

mail(m)

Takes login names and distribution group names as arguments and

mbox

Indicates that a list of messages should be sent to mbox in your home
directory when you quit. This is the default action for messages if you

sends mail to those people.

did not set the hold option.

next (n, + or CR)

Goes to the next message in sequence and types it. With an argument

list, it types the next matching message.
preserve (pre)

Takes a message list and marks each message in it to be saved in the
user’s system mailbox instead of in mbox . Synonymous with the
hold command.

print (p)

Takes a message list and types out each message on the user’s
terminal, without printing any specified ignored fields.

Print (P)

Prints a message in its entirety, including specified ignored fields.

quit (q)

Terminates the session. All undeleted, unsaved messages are saved in
the user’s mbox file in his login directory; all messages marked with
hold or preserve or that were never referenced are saved in his
* system mailbox; and all other messages are removed from his system
mailbox. If new mail arrives during the session, the user receives the

Commands 1-397

mail (1)
message: You have new mail. If given while editing a mailbox file
with the - £ flag, then the edit file is rewritten. A return to the Shell is

effected, unless the rewrite of the edit file fails, in which case the user
can escape with the exit command.

reply (r)

Takes a message list and sends mail to the sender and all recipients of
the specified message. The default message must not be deleted.

Reply (R)

Replies to originator of the message. Does not reply to other recipients

respond

Takes a message list and sends mail to the sender and all recipients of
the specified message. Synonymous with reply.

save (s)

Takes a message list and a file name and appends each message to the

of the original message.

end of the file. The messages are saved in the order in which they
appear in the mail directory, not in the order given in the message list.

The filename, which is enclosed in quotes, followed by the line count
and character count, is displayed on the user’s terminal.

set (se)

Prints all variable values when no arguments are given. Otherwise,
the set command sets the specified option. Arguments either take the
form
option=value
or

option

shell (sh)

Invokes an interactive version of the shell.

size

Takes a message list and prints out the size (in characters) of each
message. The size of the messages are printed in the order that they
appear in the mail directory, not in the order given in the list.

source (so)

Reads mail commands from a file.

top

Takes a message list and prints the top few lines of each. The number
of lines printed is controlled by the variable toplines and defaults

to five.

type (1)

Takes a message list and types out each message on the user’s
terminal, without printing any specified ignored fields. Synonymous
with print.

type (T)

Prints a message in its entirety, including specified ignored fields.

unalias

Takes a list of names defined by alias commands and cancels the

Synonymous with print.

list of users. The group names no longer have any significance.

undelete (u)

Takes a message list and marks each one as not being deleted.

unset

Takes a list of option names and discards their remembered values; the
inverse of set.

visual (v)

Takes a message list and invokes the display editor on each message.

write (w)

Takes a message list and a file name and appends each message to the

end of the file.

1-398 Commands

Synonymous with save.

mail (1)
xit (x)

Returns to the Shell without modifying the user’s system mailbox,
mbox , or edit file in —£. Synonymous with exit.
Presents message headers in windowfulls as described under the
headers command. You can move forward to the next window with
the z command. Also, you can move to the previous window by using
y

The following is a summary of the tilde escape functions that you can use when
composing mail messages. Note that you can only invoke these functions from
within the body of a mail message and that the sequences are only executed if they
are placed at the beginning of lines.
~!command
~?

Executes the indicated shell command, then returns to the message.
Prints a brief summary of tilde commands.

Executes the mail commands. (For example, the command ~:10

prints out message number 10 while ~ : - prints out the previous
message.

~C name ...

Adds the given names to the list of carbon copy recipients.

Reads the file named dead letter from your home directory into the
message.

Invokes the text editor on the message you are typing. After the
editing session is finished, you may continue appending text to the
message.

~f messages

Reads the named messages into the message being sent. If no

Edits the message header fields by typing each one in turn and
allowing the user to append text to the end or to modify the field by
using the current terminal erase and kill characters.

~m messages

messages are specified, reads in the current message.

Reads the named messages into the message being sent, shifted one
tab space to the right. If no messages are specified, reads the current
message.

Prints the message on your terminal, prefaced by the message header

Aborts the message being sent, copying the message to dead.letter in

~r filename

Reads the named file into the message.

~§ string

Causes the named string to become the current subject field.

~t name ...

Adds the given names to the direct recipient list.

fields.

your home directory if the save option is set.

Invokes an alternate editor (defined by the VISUAL option) on the
message. Usually, the alternate editor is a screen editor. After you
‘quit the editor, you can resume appending text to the end of your
message.

~w filename

Writes the message onto the named file.

~| command

Pipes the message through the command as a filter. If the command
Commands 1-399

mail (1)
gives no output or terminates abnormally, retains the original text of
the message. The command fmt(1) is often used as command to

rejustify the message.

~~string

Inserts the string of text in the message prefaced by a single tilde (~).
If you have changed the escape character, then you should double that

character in order to send it.
Options are controlled via the set and unset commands. Options may be either
binary or string. If they are binary you should see whether or not they are set; if they
are string it is the actual value that is of interest.
The binary options include the following:

append

Causes messages saved in mbox to be appended rather than
prepended. (This is set in /usr/lib/Mail.rc on version 7 systems.)

ask

Causes mail to prompt you for the subject of each message you
send. If you simply respond with a new line, no subject field is
sent.

askcc

Asks you at the end of each message whether you want to send a

carbon copy of the message to additional recipients. Responding
with a new line indicates your satisfaction with the current list.

autoprint

Causes the delete command to behave like dp — thus, after
deleting a message, the next one is typed automatically.

debug

Causes mail to output information useful for debugging mail.
Setting the binary option debug is the same as specifying —d on
the command line.

dot

Causes mail to interpret a period alone on a line as the terminator
of a message you are sending.

hold

Holds messages in the system mailbox by default.

ignore

Causes interrupt signals from your terminal to be ignored and
echoed as at signs (@).

ignoreeof

Causes mail to refuse to accept a control-d as the end of a
message.

msgprompt

Prompts you for the message text and indicates how to terminate
the message.

metoo

Includes the sender in the distribution group receiving a mail
message.

nosave

Prevents mail from copying aborted messages into the dead.letter

file in your home directory.

quiet
verbose

Suppresses the printing of the version when first invoked.
Displays the details of each message’s delivery on the user’s

terminal. Setting the verbose option is the same as typing —v on
the command line.
The string options include the following:

EDITOR

1-400 Commands

Pathname of the text editor to use in the edit command and ~e
escape. If not defined, then a default editor is used.

mail (1)
SHELL

Pathname of the shell to use in the ! command and the ~! escape.
A default shell is used if this option is not defined.

VISUAL

Pathname of the text editor to use in the visual command and
~V escape.

crt

Threshold to determine how long a message must be before more
is used to read it.

escape

folder

The first character of this option gives the character to use in the
place of tilde (~) to denote escapes, if defined.

Directory name to use for storing folders of messages. If this name
begins with a backslash (/) mail considers it an absolute
pathname; otherwise, the folder directory is found relative to your
home directory.

record

toplines

Pathname of the file used to record all outgoing mail. If it is not

defined, then outgoing mail is not so saved.

The number of lines of a message that is printed out with the top
command; normally, the first five lines are printed.

Return Values
If mail is invoked with the —e option, the following exit values are returned:
the user has mail
0
the user has no mail
1

Files
fusr/spool/mail/*
~/mbox
~/.mailrc
/tmp/R#
fusr/lib/Mail.help*
/usr/lib/Mail.rc
Message*

mail directory
your read mail
file giving initial mail commands
temporary for editor escape
help files
system initialization file
temporary for editing messages

See Also
binmail(1), fmt(1), newaliases(1), aliases(5), mailaddr(7), sendmail(8)

Commands 1-401

make (1)

Name
make, sSmake — maintain, update, and regenerate groups of programs

Syntax
make [ -f makefile ] [ options ][ names ]

sSmake [ -f makefile 1 [ options ][ names ]

Description
This is the SYSTEM V version of the make command with some Berkeley
compatibility added.

Options
-b

Compatibility mode for old makefiles.

—d

Debug mode. Displays detailed information on files and times
examined.

-0

~f makefile

Causes environment variables to override assignments within
makefiles.
Uses the specified description file name. A file name of — denotes
the standard input. The contents of the file specified as makefile

override the built-in rules.
Ignores error codes returned by invoked commands. This mode is

entered if the special target name .IGNORE appears in the
description file.
Stops work on the current entry, but continues on other branches

that do not depend on that entry.
Displays a memory map showing text, data, and the stack. Does
not operate on systems without the getu system call.
=N

No execute mode. Displays commands, but does not execute
them. Even lines beginning with an at sign (@) are printed.
Displays the complete set of macro definitions and target

descriptions.
Question mode. Returns a zero or nonzero status code depending
on whether the target file is or is not up to date.

Does not use the built-in rules.
Silent mode. Suppresses the display of command lines before
executing. This mode is also entered if the special target name
SILENT appears in the description file.

Abandon work on the current entry if it fails; the opposite of the -k
option. If both options are specified, the last one specified on the
command line is used.
Touches target files (causing them to be up to date) rather than

1-402 Commands

make (1)
issuing usual commands.

Special Names

.DEFAULT

If a file must be made but there are no explicit commands or

relevant built-in rules, the commands associated with the name
.DEFAULT are used if it exists.

PRECIOUS

Dependents of this target are not removed when quit or interrupt is

SILENT

Same effect as the —s option.

JGNORE

Same effect as the —i option.

hit.

Dependencies of the .SUFFIXES special target are added to the

SUFFIXES

table of known suffixes.

Discussion

The make program executes commands in makefile to update one or more target

names . The name argument is typically a program. If no —f option is present,
makefile, Makefile, s.makefile, and s.Makefile are tried in order. If makefile is -,
the standard input is taken. You can specify more than one —f makefile argument.
The make program updates a target only if its dependents are newer than the target.
All prerequisite files of a target are added recursively to the list of targets. Missing
files are deemed to be out of date.

The makefile argument contains a sequence of entries that specify dependencies. The
first line of an entry is a blank-separated, non-null list of targets, then a colon ),
then a (possibly null) list of prerequisite files or dependencies. Text following a
semicolon (;) and all following lines that begin with a tab are shell commands to be
executed to update the target. The first line that does not begin with a tab or number
sign (#) begins a new dependency or macro definition. Shell commands can be
continued across lines with the backslash followed by a new-line (RET) sequence.
Everything printed by make (except the initial tab) is passed directly to the shell.
For example:
echo a\
b

These entries produce the following:
ab

This output is exactly the same as what would have been produced by the shell.
Number sign (#) and new-line surround comments.

The following makefile says that pgm depends on two files a.o and b. o, and that
they in turn depend on their corresponding source files (a.c and b.c) and a
common file incl.h:

pgm:

a.o b.o

cc a.o b.o -o pgm
a.o: incl.h a.c
cc

b.o:
cc

-c

a.c

incl.h b.c
-c b.c

Commands 1-403

make (1)
Command lines are executed one at a time, each by its own shell. The first one or
two characters in a command can be the following: —, @, -@, or @-. If @ is

present, printing of the command is suppressed. If — is present, make ignores an
error. A line is printed when it is executed unless the —s option is present, or the
entry .SILENT: is in makefile, or unless the initial character sequence contains a @.

The —n option specifies printing without execution. However, if the command line
has the string $(MAKE) in it, the line is always executed (see discussion of the

MAKEFLAGS macro under Environment). The -t (touch) option updates the
modified date of a file without executing any commands.

Commands returning nonzero status normally terminate make. If the —i option is
present, or the entry IGNORE: appears in makefile, or the initial character sequence

of the command contains —, the error is ignored. If the —k option is present, work
stops on the current entry, but continues on other branches that do not depend on that

entry.

The -b option allows old makefiles (those written for the old version of make) to run

without errors. The difference between the old version of make and this version is
that this version requires all dependency lines to have a (possibly null or implicit)
command associated with them. The previous version of make assumed, if no

command was specified explicitly, that the command was null.

Interrupt and quit cause the target to be deleted unless the target is a dependent of the

special name .PRECIOUS.

Environment
The environment is always read by make.

All variables are assumed to be macro
definitions and processed as such. The —e option causes the environment to override
the macro assignments in a makefile.
The make command operates in three compatibility modes.

The type of mode is
determined by value of the PROG_ENYV environment variable and by the way that

make is executed. The PROG_ENYV variable has three valid values:
o

BSD

POSIX

SYSTEM_FIVE

In BSD mode, make executes with Berkeley compatibility. This means that

/bin/sh is always used as the command interpreter regardless of the value of
SHELL, and the commands are echoed to standard out without a prefixed <tab>.

In POSIX mode, make executes with POSIX compatibility, such that the SHELL
environment variable is always ignored, SHELL is always overridden by
MAKESHELL, the shell is always used to execute commands, and commands are
echoed to standard out with a prefixed <tab>.

SYSTEM_FIVE mode causes make to run with SYSTEM V compatibility such that

SHELL is used to execute commands and commands are echoed to standard out with
a prefixed <tab>.
'

For all modes, SHELL has a default value of / bin// sh. When make is executed

with the command name s5make, it always executes in SYSTEM_FIVE mode and
ignores the environment variable PROG_ENYV.

1-404 Commands

make (1)
The MAKEFLAGS environment variable is processed by make as containing any
legal input option (except —f, —p, and —d ) defined for the command line. Further,
upon invocation, make invents the variable if it is not in the environment, puts the
current options into it, and passes it on to invocations of commands. Thus,
MAKEFLAGS always contains the current input options. This proves very useful for
super-makes. In fact, as noted above, when the -n option is used, the command
$(MAKE) is executed anyway. Hence, one can perform a make —n recursively on a

whole software system to see what would have been executed. This is because the
-n is put in MAKEFLAGS and passed to further invocations of $(MAKE). This is
one way of debugging all of the makefiles for a software project without actually
doing anything.

Macros

Macros can be defined in four different ways. Some macros are defined by default by
make internally. All environment variables are assumed to be macro definitions and
macros can be defined in the makefile as well as on the make command line. By
default, the internal default macros are overridden by environment variables, macros
defined in the makefile override environment variables and macros defined on the
command line override macros defined in the makefile. The -e option changes this
such that environment variables override macros defined in the makefile.
Entries of the form stringl = string2 are macro definitions. String2 is defined as all
characters up to a comment character or an unescaped new-line. Subsequent
appearances of $( stringl [: substl =[ subst2]]) are replaced by string2 . The
parentheses are optional if a single character macro name is used and there is no
substitute sequence. The optional : subst] = subst2 is a substitute sequence. If it is
specified, all non-overlapping occurrences of subst/ in the named macro are replaced
by subst2. The occurrence of subst] must be a suffix at the end of the word stringl.
Strings (for the purposes of this type of substitution) are delimited by blanks, tabs,
new-line characters, and beginnings of lines. An example of the use of the substitute
sequence is shown under Libraries.

The MACHINE macro is defined by make to allow for machine independent
makefiles. The legal values are: vax or mips.

Internal Macros

There are five internally maintained macros which are useful for writing rules for
building targets.

The macro $* stands for the file name part of the current
dependent with the suffix deleted. It is evaluated only for
inference rules.

The $@ macro stands for the full target name of the current target.

The $< macro is only evaluated for inference rules or the
DEFAULT rule. It is the module which is out-of-date with

It is evaluated only for explicitly named dependencies.

respect to the target (that is, the manufactured dependent file
name). Thus, in the .c.o rule, the $< macro would evaluate to the
.c file. An example for making optimized .o files from .c files is:
.C.O:

cc -¢c -0

$*.c

or.

Commands 1-405

make (1)
.C.O:

cc -¢c

-0

The $? macro is evaluated when explicit rules from the makefile
are evaluated. It is the list of prerequisites that are out of date with

respect to the target; essentially, those modules which must be
rebuilt.

The $% macro is only evaluated when the target is an archive
library member of the form lib(file.0). In this case, $@ evaluates
to lib and $% evaluates to the library member, file.o.

Four of the five macros can have alternative forms. When an upper case D or F is
appended to any of the four macros, the meaning is changed to directory part for D

and file part for F. Thus, $(@D) refers to the directory part of the string $@. If
there is no directory part, ./ is generated. The only macro excluded from this
alternative form is $?. The reasons for this are debatable.

Suffixes
Certain names (for instance, those ending with .0) have prerequisites such as .c, .s,
which can be inferred. If no update commands for such a file appear in makefile, and
if an inferable prerequisite exists, that prerequisite is compiled to make the target. In
this case, make has inference rules which allow building files from other files by
examining the suffixes and determining an appropriate inference rule to use. The
current default inference rules are:
.¢c

.¢c~

.y~.0

.sh

.sh~

.1l.0

.1~.0

.c.o0
.y.c

.c~.0
.y~.c

.c~.C

.S.0

.8~.0

.y.O

.l.c

.c.a

.c~.a

.s~.a

.h~.h

The internal rules for make are contained in the source file rules.c for the make
program. These rules can be locally modified. To print out the rules compiled into
make in a form suitable for recompilation, the following command is used from
/bin/sh:
make

-fp

2>/dev/null

</dev/null

The only peculiarity in this output is the (null) string which print £(3s) prints when
handed a null string.
A tilde in the above rules refers to an SCCS file. Thus, the rule .c~.0 would
transform an SCCS C source file into an object file (.0). Because the s. of the SCCS

files is a prefix, it is incompatible with the make suffix point-of-view. Hence, the
tilde is a way of changing any file reference into an SCCS file reference.
A rule with only one suffix (that is, .c:) is the definition of how to build x from x.c.

In effect, the other suffix is null. This is useful for building targets from only one
source file (for example, shell procedures, simple C programs).
Additional suffixes are given as the dependency list for .SUFFIXES. Order is
significant; the first possible name for which both a file and a rule exist is inferred as
a prerequisite. The default list is:
.SUFFIXES:

Here again, the above command for printing the internal rules display the list of
suffixes implemented on the current machine. Multiple suffix lists accumulate;
SUFFIXES: with no dependencies clears the list of suffixes.

1-406 Commands

make (1)

Inference Rules
The first example can be done more briefly.
pgm:

a.o b.o

cc a.o b.o -o pgm
a.o b.o: incl.h

This is because make has a set of internal rules for building files. The user may add
rules to this list by simply putting them in the makefile.

Certain macros are used by the default inference rules to permit the inclusion of
optional matter in any resulting commands. For example, CFLAGS, LFLAGS, and
YFLAGS are used for compiler options to cc(1), lex(1), and yacc(l), respectively.
Again, the previous method for examining the current rules is recommended.

The inference of prerequisites can be controlled. The rule to create a file with suffix
.0 from a file with suffix .c is specified as an entry with .c.0: as the target and no
dependents. Shell commands associated with the target define the rule for making a
.0 file from a .c file. Any target that has no slashes in it and starts with a dot is
identified as a rule and not a true target.

Libraries

If a target or dependency name contains parentheses, it is assumed to be an archive
library, the string within parentheses referring to a member within the library. Thus
lib(file.0) and $(LIB)(file.0) both refer to an archive library which contains file.o.
(This assumes the LIB macro has been previously defined.) The expression
$(LIB)(filel.o file2.0) is not legal. Rules pertaining to archive libraries have the form
XX .a where the XX is the suffix from which the archive member is to be made. An
unfortunate byproduct of the current implementation requires the XX to be different
from the suffix of the archive member. Thus, one cannot have lib(file.o) depend
upon file.o explicitly. The most common use of the archive interface follows. Here,
we assume the source files are all C type source:

1ib: lib(filel.o) lib(file2.0) lib(file3.o)
@echo lib is now up-to-date
.C.a:

$(CC)

-c $(CFLAGS1)

rm —-f

$*.0

ar rv $@

$*.o0

In fact, the .c.a rule listed above is built into make and is unnecessary in this

example. A more interesting, but more limited example of an archive library
maintenance construction follows:

lib: lib(filel.o) lib(file2.0) lib(file3.o)
$(CC) -c $(CFLAGS) $(?:.o0=.cC)
ar rv lib

§?

rm $°?

@echo lib is now up-to-date
.C.azi;

Here the substitution mode of the macro expansions is used. The $? list is defined
to be the set of object file names (inside lib) whose C source files are out-of-date.
The substitution mode translates the .0 to .c. (Unfortunately, one cannot as yet
transform to .c~; however, this may become possible in the future.) Note also, the
disabling of the .c.a: rule, which would have created each object file, one by one.

This particular construct speeds up archive library maintenance considerably. This

Commands 1-407

make (1)
type of construct becomes very cumbersome if the archive library contains a mix of
assembly programs and C programs.

Restrictions
Some commands return non-zero status inappropriately; use —i to overcome the

difficulty. File names with the characters = : @ do not work. Commands that are
directly executed by the shell, notably cd(1), are ineffectual across new-lines in
make. The syntax (lib(filel.o file2.0 file3.0) is illegal. You cannot build lib(file.o)
from file.o. The macro $(a:.0=.c~) does not work.

Files
[Mm]akefile and s.[Mm]akefile

See Also
cc(1), ed(1), lex(1), sh(1), yacc(1), s5make(1)

1-408 Commands

man(1)

Name
man — displays manual pages online

Syntax
man -k keyword...
man —f page _title...
man [ options 1 [ —roff options ]... [ section ] page_title...
man [ options ][ section page _title... ]...

/usr/bin/man [ option ][ section ] page _title...
fusr/bin/man [ options ][ section page title... ]...

Description
There are two man commands: /usr/ucb/man, and /usr/bin/man. For most
users, /usr/ucb/man is the default man command. The command
which man

shows you which man command is the default. The recommended default is
/usr/ucb/man.

Both the man commands provide online displays of specified reference pages.

The /usr/ucb/man Command.
The basic function of this command is to provide online displays of reference pages.
You can use options, however, to direct the man command to display one line
summaries of reference pages which contain specific keywords, to display one line
summaries of specific reference pages, to use special formatting options when
preparing the reference page for display or printing, and to search alternate reference
page directories for specified reference pages.

If an option is not used, the man command formats and displays one or more
specified reference pages. If there are multiple reference pages which match a

specified name, only the first matching reference page is displayed. If there are
multiple matches in a section for a specified name, the matching page in the first
alphabetically occurring subsection is displayed.

If you specify the man command with a section argument, the man command looks
in that section of the reference pages for the specified page titles. A section consists
of a number in the range O to 9, optionally followed by an alphanumeric subsection,
or section can be the name ‘local’, ‘new’, ‘old’, or ‘public’. Numbers O and 9 are
non-standard. If a sect ion is omitted, the man command searches all sections of
the reference pages. The man command displays commands (both standard and
local) over subroutines in system libraries, and displays the first occurrence it finds, if
any. If Section 1 is specified, the sections n, 1, and o are also searched, if they exist.

The section and page_title... arguments can be paired, so that multiple pages can be
searched for in a section, and multiple sections can be searched for a page or pages.

All displays are directed to standard out, unless redirected, or unless the —t option is
specified. If the standard output is a teletype device, the man command completes
the following: pipes the output through the cat(1) command using the option —s to
eliminate unnecessary blank lines and invokes the page(1) command using the
Commands 1-409

man(1)
option —s to display a screen at a time.
If a specified reference page is not already formatted, but the source file exists, the
man command preprocesses the file through the tb1(1) command. The command

next pipes the output to the nrof £(1) command, or to the t rof f command if the
-t option was specified, using the man(7) macros package. If the tbl output was
directed to the nrof £ command, the output is then piped through the col1(1)
postprocessor, then directed to standard out. If the appropriate

/usr/man/cat?

directory exists, the formatted display is saved there.

The /usr/bin/man Command
The /usr/bin/man command performs the same basic function as the
/usr/ucb/man command, that is, formats and displays or prints specified reference
pages. It does not provide all the functions of /usr/ucb/man, and there are some

differences in common functions.
The /usr/bin/man command searches for the specified reference pages, and

formats and displays all reference pages matching the specified names. If no section
is specified, all sections 1 through 8 are searched. In the case of multiple matches,
the display order is in numeric section order, and ASCII subsection order within a
section.
All displays are directed to standard out, unless redirected, or unless an option is used
which requests processing through the t rof £ command. If a troff option was not
specified, then the standard output is to a teletype device. If the standard output is a
teletype device, the /usr/bin/man pipes the output through the col(1)
postprocessor, then directs the output to standard out.
The /usr/bin/man command does not use preformatted files. It searches only the
/usr/man/man[1-8] directories for source files.

If a specified file exists, it is always preprocessed through the tb1(1) command.
If an option is not used, the /usr/bin/man command formats and displays
specified reference pages using the nrof£ command.

If multiple options are specified, only the last one is executed, except that multiple
~roff _options are accepted and executed.

Options
/usr/ucb/man Options
The following options are recognized only by the /usr/ucb/man command. Note
that the options — and -k do not have the same functionality as the corresponding

/usr/bin/man options.
-

Squeeze multiple blank lines from output.

—f

Display one line summaries of each page title specified on the
command line.

-k

Display one line summaries of each reference page that contains the
specified keyword or keywords.

~P manpath

Search the specified manpath directory instead of /usr/man.

-S

Remove unnecessary blank lines.

1-410 Commands

man(1)
Phototypesets the output through the t rof £ command.

This option requires the installation of the t rof £ command, which is
unsupported. When the —t option is specified, the t rof £ output is
directed, by 1pr’s —t option, to the printer or typesetter specified by
the PRINTER environment variable. PRINTER must be set to a
printer which is capable of handling t rof £ output files. The default
is the lp printer (see 1pr(1) description of the —t option for more
information).

/usr/bin/man Options

The following options are recognized by the /usr/bin/man command. Note that
the options — and —k do not have the same functionality as the corresponding
/usr/ucb/man options.

—roff options Inserts the specified roff_option in front of the —man option when the
appropriate *roff text formatter is called (the other options determine
which *roff formatter is called). Multiple roff options can be
specified. If a null value is specified, the results are unpredictable.

—e | —et | —te

Preproceses the display with the eqn command, then performs the
same steps as the —t option.

This option requires the installation of the eqn and troff
commands, which are unsupported.

—ek | ke

Preproceses the display with the eqn command, then performs the
same steps as the —k option.

This option requires the installation of the eqn, tc, and troff
commands, which are unsupported.
-k

Formats the display through the t rof£ command, using troff’s -t
option, then directs the output to the tc command.

This option requires the installation of the tc and trof f commands,
which are unsupported.

Formats the display through the nroff command. This is the default.
Preproceses the display with the neqn command, then performs the
same steps as the —n option.

This option requires the installation of the negqn command, which is
unsupported.

Photypesets the output through the t rof f command.

This option requires the installation of the t rof f command, which is
unsupported.

Shows where the specified reference pages are located, relative to the
/usr/man directory.

Restrictions
The reference pages are reproducible on phototypesetters or on hardcopy devices.
However, some devices do not properly handle special characters which causes
information to be lost.

Commands 1-411

man (1)
Some options require the installation of unsupported software. Use of these options
is at your own risk.
Options which call the negn or eqn commands will generally fail when used with
the ULTRIX reference pages, because any ULTRIX reference pages which use *eqn
commands were preprocessed through the neqgn text formatter before being packaged
for shipment to you. *eqn text preprocessors generally report numerous errors when
attempts are made to reprocess files a second time through an *eqn text
Preprocessor.

Both /usr/ucb/man and /usr/bin/man commands cd to the /usr/man

directory before searching for and formatting files. Some reference pages assume that
this happens. Therefore, an attempt to format some reference pages manually with a
*rof £ text formatter may fail if you are not sitting in the /usr/man directory.

/usr/ucb/man Restrictions
If a specified reference page exists in the appropriate /usr/man/man? directory,
but there is no appropriate /usr/man/cat? directory, you will not be able to
scroll backwards in the display.
The man directories for sections n, 1, o, p, 0 and 9 are optional directories. They must
be created by the system administrator.
The /usr/man/cat? directories are not required to exist. They must be created

by the system administrator. This is generally done through the catman(8)
command.

Examples
/usr/ucb/man Examples
The following examples all assume the use of the default command:

/usr/ucb/man.
The following example shows how to locate reference pages containing the keyword

‘graph’:
% man

-k graph

The following example shows how to display the graph(1g) reference page:
%

man

lg graph

The following example shows how to display plot reference pages:
% man

plot

The following example shows how to display chmod and chown reference pages:
% man

chmod

chown

chmod

chown

The following example shows how to display a reference page test in the
/usr/man/manl directory. In order to locate the test reference page here, it
must have the file name test . 1, so its reference page title would be test(l).
% man

local

test

To locate the test reference pages in Section 1:
% man

1-412 Commands

test

1sh5

test

man (1)
If you have a directory /usr/local/man which contains man? subdirectories,
which also contain reference pages, then the following example shows how to display
a reference page games located somewhere in a subdirectory of
/usr/local/man:
$ man -P

/usr/local games

/usr/bin/man Examples
The following example shows how to display chmod reference pages:
$

/usr/bin/man chmod

The above displays all the chmod reference pages from all sections of the installed
reference pages.

The following example shows how to display all the test reference pages in
Section 1:
%

/usr/bin/man 1 test

The following example shows how to locate all the test reference pages:
$

/usr/bin/man -w test

The following example shows how to locate all the int ro reference pages in
Section 3:
%

/usr/bin/man -w 3 intro

The following example displays the man(1) reference page with a starting page
number of 10.
%

/usr/bin/man -nl0

1 man

Files

/usr/ucb/man

The default man command.

/usr/bin/man

The alternate man command.

/usr/man/man?/*

These directories contain the online reference pages which

/usr/man/cat?/*

These directories contain the files generated by the man and

/usr/lib/whatis

This file contains the summary lines of each reference page.

are divided into sections 1 through 8, n, 1, 0, and p. Sections
0 and 9 can also exist but these are non-standard sections.
catman commands.

Commands 1-413

man (1)
manpath/man/man? /*

These directories contain reference pages to be searched by
the man command when the —P manpath option is specified.
These directories must have the same organization and
format as /usr/man.

See Also
apropos(1), col(1), man(7), nroff(1), page(1), tbl(1), whatis(1), whereis(1), catman(8)

1-414 Commands

mark (1mh)

Name
mark — mark messages

Syntax
mark [+foldername] [msgs] [-sequence name...] [-add] [-delete] [-list] [-public]
[-nopublic] [-zero] [-nozero] [-help]

Description
Use the mark command to assign a name to a sequence of messages within the
current folder. You can then use this message sequence with any MH command that
takes a msg or msgs argument.

The following example shows how you can create a message sequence called “‘out’
containing messages 10-20 in the current directory. The second part of the example
shows how this sequence can be used in conjunction with the rmm command, to
delete all the messages in the sequence.
% mark
%

10-20

-sequence out

rmm out

You can specify a folder other than the current folder, by using the <+folder>
argument.

Sequences still point to the same messages even if you sort all the messages in the
folder with sortm.

If you delete a message or refile it in another folder, it is also deleted from the
sequence.

You can use mark in conjunction with pick to give you a very powerful and
flexible way to manipulate messages. The following example shows how you can
combine the two commands together to select all messages from Adrian and put them
in a sequence named Ateam. See pick(1mh) for more details of the power of
pick.
mark

‘pick

-from Adrian‘'

-sequence Ateam

Note that you cannot use special characters, such as hyphens, in sequence names.
Sequence names can consist of alphanumeric characters, but the first character must
be alphabetic.

If you create a sequence using mark, the ordering of messages within the folder
remains unchanged. So if messages 3, 7 and 9 are put into the sequence, they are
still shown as messages 3, 7 and 9 if you use scan after incorporating them into the
sequence. The scan command does not show any differences between messages
that are in sequences and ordinary messages within a folder.

Options
If you use mark on its own without specifying —sequence name, it displays the
sequences that have been created in the current folder. The following example shows
how this works. It also illustrates that one message can be in more than one
sequence at the same time.

Commands 1-415

mark (1mh)
%

mark

cur:

one:

Two:

2-4

An identical result can be obtained if you use mark-list

A message sequence is a keyword, just like one of the reserved message names,
such as first or next. Unlike the reserved message names, you can define,
modify, and remove the semantics of a message sequence. Message sequences are
folder-specific, for example: the sequence name seen in folder +inbox need not
have any relation whatsoever to the sequence of the same name in a folder of a
different name.

You can manipulate sequences with three options:
-add

~delete

-list

These switches are mutually exclusive: the last occurrence of any of them overrides
any previous occurrence of the other two.
The —add switch tells mark to add messages to sequences or to create a new
sequence. For each sequence named via the ~sequence <name> argument the
messages named in <msgs> (which defaults to the current message if no msgs are
given), are added to the sequence. The messages to be added need not be absent

from the sequence. If you specify the —zero option, all messages in the sequence
are removed from the sequence, before the new messages are added to it. Note the
messages are removed from the sequence only. They are not deleted or removed
from your folder.

If you specify —add-nozero the specified messages are appended to the sequence.
The —delete switch tells mark to delete messages from sequences, and is the
opposite of —add. For each of the specified sequences, the named messages are
removed from the sequence. These messages need not be already present in the
sequence. If the —zero switch is specified, then all the messages in the folder are
appended to the sequence prior to the removal of the messages. The following
example shows how this works in a folder with sixteen messages.
% mark

-delete

-zero

-sequence

notseven

% mark

notseven:

1-6

8-16

Hence, ~delete -zero means that each sequence should contain all messages
except those indicated, while —-delete -nozero means that only the indicated
messages should be removed from each sequence. As expected, the command
mark -sequence seen -delete all deletes the sequence seen from the
current folder.

When creating (or modifying) a sequence, the —public switch indicates that the
sequence should be made readable for other MH users. In contrast, the —-nopublic
switch indicates that the sequence should be exclusive to your MH environment.
The —1ist switch tells mark to list the sequences defined for the folder and the
messages associated with those sequences.

1-416 Commands

mark(1mh)
You can list each sequence named by using the —sequence name switch. If you
do not specify the sequence name, ~1ist lists all sequences, and the messages
associated with those sequences, in the specified folder. The —zero switch does not
affect the operation of -1ist.

The name used to denote a message sequence must consist solely of alphabetic
characters, and cannot be one of the reserved message names (such as, first cur
and so forth).

You can define up to a maximum of 10 sequences in any one folder.
The name used to denote a message sequence cannot occur as part of a message
range: for example, constructs like seen:20 or seen -10 are forbidden.
The defaults for this command are:
+folder defaults to the current folder

-add if msgs is specified, -1ist otherwise
msgs defaults to cur (or all if ~1ist is specified)
-nopublic if the folder is read—only, ~public otherwise
—nozero

Files
$HOME/.mh_profile

Your user profile

Profile Components
Path:

Current-Folder:

To your MH directory

To find the default current folder

See Also
folder(1mh), pick(1mh), sortm(1mh)

Commands 1-417

VAX

mdtar(1)

Name
mdtar — multivolume archiver

Syntax
mdtar [ key] [ name... ]

Description
The mdt ar command saves multiple files on multiple archives (usually an RX50
diskette, but any file/device may be specified). mdtar actions are controlled by the
key argument. The key is a string of characters containing one function letter and
one or more function modifiers.

Other arguments to mdtar are file or directory

names specifying which files to dump or restore. In all cases, appearance of a
directory name refers to the files and, recursively, subdirectories of that directory.
mdtar also saves special files.

Options
-C

Changes directory to specified name.

This allows multiple directories

not related by a close common parent, to be archived using short relative
path names. For example, to archive files from /usr/include and

from /etc, one might use
tar

-C

/usr

include

-C

/etc

The function portion of the key is specified by a letter.
C

Creates a new archive. Writing begins at the beginning of the archive
instead of after the last file.

Writes the named files to the end of the archive.
If no file argument is given, all Generates archive table of contents. If
no argument is given, all of the names on the archive are listed. Produce

a Table of contents.
Updates the current archive. Adds the named files to the archive, if they
are not there already or if they have been modified since last put on the
archive.

Extracts each specified file from the archive. If the named file matches a
directory whose contents had been written onto the archive, this directory
is recursively extracted. The owner, modification time, and mode are
restored if you are the superuser and if you have also specified the p

switch. If no file argument is given, the entire content of the archive is
extracted. If multiple entries specifying the same file are on the archive,
the last one overwrites previous versions.
The following characters may be used to qualify the function desired in addition to
one or more of the above letters.

0..9

Selects unit number of the drive as an alternate disk drive. The default

disk drive is the device named /dev/rrala.
A

1-418 Commands

Uses the specified number (next argument) as archive with which to

mdtar (1)
begin the output. This switch is intended for error recovery. mdtar

outputs files in terms of Archives. Each Archive contains a number of
files. If mdtar has been requested to dump a path (set of files) that
consist of (for example) 10 archives and there is an error writing the nth
Archive, then the A modifier may be used to restart mdtar at the nth
Archive.

CAUTION

You must issue the same path (set of files) as in the first command. This
will guarantee that mdtar will begin at the correct file on Archive n.
If the v mode is specified, mdtar outputs informational messages to inform the user
of progress. For example, the following command will dump the entire directory
structure:
mdtar

If an error occurs on Archive 7, to restart at the 7th Archive, without having to redump the first 6 Archives, issue the following command:
mdtar cvA 7

mdtar will tell you it is skipping the first 6 Archives and will resume output with
the data that begins Archive 7.
b

Uses the specified number (next argument) as the blocking factor. The

Forces output blocking to 20 blocks per record.

Uses the specified file (next argument) as the name of the archive. If the

F[F]

Operates in fast mode. When F is specified, mdtar skips all SCCS
directories, core files, and errs files. When FF is specified, mdtar also

default is 20 (the maximum is 20).

name of the file is —, tar writes to standard output (piping).

skips all a.out and *.0 files.

Saves a copy of the file (excludes symbolic links). The default action of
mdtar is to place symbolic link information on the output device. A
copy of the file IS NOT saved on the output device.
Ignores checksum errors found in the archive.

Displays an error message if all links to the files dumped cannot be
resolved. If -1 is not specified, no error messages are printed.
Does not restore file modification times. The modification time is the

time of extraction. Normally, mdtar restores modification times of

regular and special files.

Suppresses the normal directory information. On output, mdtar

normally places information specifying owner and modes of directories
in the archive. Former versions of tar, when encountering this
information will give the error message
<name>/:

cannot

create.

Restores the named files to their original modes, ignoring the present

umask(2). Setuid and sticky information will also be restored to the
super-user. You must be Superuser to perform this option. For further
Commands 1-419

VAX

mdtar(1)
information, see stat(2), S_ISVTX.
Uses specified number (next argument) as size of media in 512-byte
blocks. This enables mdtar to be used with devices of different
physical media sizes. The default is 800 blocks (assumption is an RX50
output Archive).

Displays detailed (verbose) information as it archives files. Normally
mdtar does its work silently. With the t function, the verbose option
gives more information about the archive entries than just their names.
#cd

#tar cvf tar-out vmunix

Produces the output ‘‘a vmunix 1490 blocks’’ where 1490 is the number
of 512 byte blocks in the file ‘‘vmunix’’.
$#tar xvf tar-out

Produces the output ‘‘x vmunix, 762880 bytes, 1490 blocks’’ where

762880 is the number of bytes and 1490 is the number of 512 byte

blocks in the file ‘‘vmunix’’ which was extracted.
Displays action to be taken for each file and prompts for confirmation. If
a word beginning with ‘y’ is given, the action is done. Any other input

means do not do it.

Restrictions
The u option can be slow.

The current limit on file name length is 100 characters.
There is no way to follow symbolic links selectively.

Diagnostics
Indicates bad key characters and archive read/write errors.
Indicates if enough memory is not available to hold the link tables.

Files
/tmp/tar*

See Also

cp(1), In(1)

1-446 Commands

nawk (1)

Name
nawk — data transformation, report generation language

Syntax
nawk [ —f programfile 1 [ —Fs 1[ program ][ var=value... 1]

file ... ]

Description
The nawk language is a file-processing language which is well-suited to data
manipulation and retrieval of information from text files. This reference page
provides a full technical description of nawk; if you are unfamiliar with the language, you will probably find it helpful to read the Guide to the nawk Utility
before reading the following material.
A nawk program consists of any number of user-defined functions and ‘rules’ of the
form:
pattern

{action}

There are two ways to specify the nawk program:
(a)

(b)

Directly on the command line. In this case, the program is a single
command line argument, usually enclosed in apostrophes ().

By using the —f programfile option (where programfile contains the nawk
program). More than one —f option can appear on the command line. The
program will consist of the concatenation of the contents of all the specified
programfiles. You can use — in place of a file name, to obtain input from the
standard input.

The input data manipulated by the nawk program is provided in files specified on the
command line. If no such files are specified, data is read from the standard input.
You can also specify a file name of — to mean the standard input.

Input to nawk is divided into records. By default, records are separated by new-line
characters; however, you can specify a different record separator if you wish.
One at a time, and in order, each input record is compared with the pattern of every
‘rule’ in the nawk program. When a pattern matches, the action part of the rule is
performed on the current input record. Patterns and actions often refer to separate
fields within a record. By default, fields are separated by white space (blanks, newlines, or horizontal tab characters); however, you can specify a different field
separator string using the —F's option (see Input).

You can omit the pattern or action part of a nawk rule (but not both). If pattern is
omitted, the action is performed on every input record (as if every record matches).
If action is omitted, every record matching the pattern will be written to the standard
output.

If a line in a nawk program contains a ‘#’ character, the ‘#’ and everything after it is
considered to be a comment.

Program lines can be continued by adding a backslash \’ to the end of the line.
Statement lines ending with a comma °,’, double or-bars ‘II’, or double ampersands
‘&&’, are automatically continued.

Commands 1-447

nawk(1)

Options
~f programfile
Tells nawk to obtain its program from the specified file. There can be
more than one of these on the command line.
-Fs

Says that s is the field separator character within records.

Variables and Expressions
There are three types of variables in nawk: identifiers, fields, and array elements.
An identifier is a sequence of letters, digits, and underscores beginning with a letter
or an underscore.

Fields are described in the Input subsection.
Arrays are associative collections of values called the elements of the array. Array
elements are referenced with constructs of the form
identifier [ subscript]

where subscript has the form expr or expr,expr,... Each such expr can have any string

value. Arrays with multiple expr subscripts are implemented by concatenating the
string values of each expr with a separator character SUBSEP separating multiple
expr. The initial value of SUBSEP is set to 034’ (ASCII field separator).

Fields and identifiers are sometimes called scalar variables to distinguish them from
arrays.

Variables are not declared and need not be initialized. The value of an uninitialized
variable is the empty string. Variables can be initialized on the command line using
var=value

Such initializations can be interspersed with the names of input files on the command
line. Initializations and input files will be processed in the order they appear on the
command line. For example, the command
nawk

-f progfile A=1

A=2

f£3

sets A to 1 before input is read from f1 and sets A to 2 before input is read from f3.
Certain built-in variables have special meaning to nawk, as described in later
sections.
Expressions consist of constants, variables, functions, regular expressions and
‘subscript in array’ conditions (see below) combined with operators. Each variable

and expression has a string value and a corresponding numeric value; the value
appropriate to the context is used. If a string is used in a numeric context, and the
contents of the string cannot be interpreted as a number, the ‘value’ of the string is
taken to be zero.

Numeric constants are sequences of decimal digits.

String constants are quoted, as in "x". Escape sequences accepted in literal strings
are:

1-448 Commands

Escape
\a

ASCIH Character
audible bell

\b
\f

backspace
formfeed

nawk (1)
\n

new-line

\r
\t

carriage return
horizontal tab

vertical tab

\ooo
\xdd

octal value ooo
hexadecimal value dd

\"
\¢

quotation mark

any other character ¢

The regular expression syntax understood by nawk is the extended regular
expressions of the egrep utility described in grep(1). Characters enclosed in slash
characters ¢/’ are compiled as regular expressions when the nawk program is read.
In addition, literal strings and variables are interpreted as dynamic regular
expressions on the right side of a ‘~’ or ‘!~’ operator, or as certain arguments to
built-in matching and substitution functions. Note that when literal strings are used
as regular expressions, extra backslashes are needed to escape regular expression
metacharacters because the backslash is also the literal string escape character.
The ‘subscript in array’ condition is defined as:
index in array

where index looks like expr or (expr,....expr). This condition evaluates to 1 if the
string value of index is a subscript of array, and to 0 otherwise. This is a way to
determine if an array element exists. If the element does not exist, this condition will
not create it.

Symbol Table
The symbol table can be accessed through the built-in array SYMTAB.
SYMTABR [expr]

is equivalent to the variable named by the evaluation of expr. For example,
SYMTAB["var"]

is a synonym for the variable var.

Environment
A nawk program can determine its initial environment by examining the ENVIRON
array. If the environment consists of entries of the form:
name=value

then
ENVIRON [name]

has string value
"value"

For example, the following program is equivalent to the default output of env(1):
BEGIN

{

for

in ENVIRON)

printf ("$s=%s\n",

ENVIRON[i])

exit

Commands 1-449

nawk (1)
Operators
The usual precedence order of arithmetic operations is followed unless overridden
with parentheses; a table giving the order of operations appears at the end of the

Guide to the nawk Utility. The unary operators are
-

Negation

Nothing (place holder)

Decrement by one
Increment by one

where the ‘++’ and ‘——’ operators can be used as either postfix or prefix operators, as
in C.
The binary arithmetic operators are
+

Addition

*
/

Subtraction
Multiplication
Division
Modulus
Exponentiation

%
~

The conditional operator
expr
? exprl

expr2

evaluates to exprl if the value of expr is non-zero, and to expr2 otherwise.
If two expressions are not separated by an operator, their string values are
concatenated.
The operator ‘~’ yields 1 (true) if the regular expression on the right side matches the
string on the left side. The operator ‘!~’ yields 1 when the right side has no match
on the left. To illustrate:
$2 ~ /10-9]/

selects any line where the second field contains at least one digit. Any string or
variable on the right side of ‘~’ or ‘!~’ is interpreted as a dynamic regular expression.
The relational operators are the usual ‘<’, ‘<=, >’, *>=’, ‘==", and ‘!=".
The boolean operators are ‘I’ (or), ‘&&’ (and), and ‘!’ (not).
Values can be assigned to a variable with
var

expr

If op is a binary arithmetic operator,
var

op=

expr

is equivalent to
var

var

expr

Command Line Arguments
The built-in variable ARGC is set to the number of command line arguments. The
built-in array ARGV has elements subscripted with digits from zero to ARGC-1,
giving command line arguments in the order they appeared on the command line.

1-450 Commands

nawk (1)
The ARGC count and the ARGV vector do not include command line options
(beginning with ‘~’) or the program file (following —£). They do include the name
of the command itself, initialization statements of the form
var=value

and the names of input data files.

The nawk language actually creates ARGC and ARGV before doing anything else.
It then walks through ARGV processing the arguments. If an element of ARGV is
the empty string, it is simply skipped. If it contains an equals sign ‘=’ it is
interpreted as a variable assignment. If it is a minus sign ‘-, it stands for the
standard input and input is immediately read from the standard input until end-of-file
is encountered. Otherwise, the argument is taken to be a file name; input will be read
from that file until end-of-file is reached. Note that the program is executed by
‘walking through’ ARGV in this way; thus if the program changes ARGV, different
files can be read and assignments made.

Input

Input is divided into records. Each record is separated from the next with a record
separator character. The value of the built-in variable RS gives the current record
separator character; by default, it begins as the new-line “n’. If you assign a different
character to RS, nawk will use that as the record separator character from that point
on.

Records are divided into fields. Each field is separated from the next with a field
separator string, given by the value of the built-in variable FS. You can set a
specific separator string by assigning a value to FS or by specifying the -Fs option
on the command line. FS can be be assigned a regular expression. For example,
FS

"[,:s]"

says that fields can be separated by commas, colons, or dollar signs. As a special
case, assigning FS a string containing only a blank character sets the field separator
to white space. In this case, any sequence of contiguous space and/or tab characters
is considered a single field separator. This is the default for FS. However, if FS is
assigned a string containing any other character, that character designates the start of
a new field. For example, if we set
F S= " \t "

(the tab character),
texta \t textb \t

\t textc

contains five fields, two of which only contain blanks. With the default setting, the
above would only contain three fields because the sequence of multiple blanks and

tabs would be considered a single separator.

Various pieces of information about input are provided by the built-in variables listed

below.

NF
NR
FILENAME
FNR

Number of fields in the current record
Number of records read so far
Name of file containing current record
Number of records read from current file

Commands 1-451

nawk (1)
Field specifiers have the form $i where i runs from 1 through NF. Such a field
specifier refers to the ith field of the current input record. $0 (zero) refers to the
entire current input record.
The getline function can read a value for a variable or $0 from the current input,
from a file, or from a pipe. The result of getline is an integer indicating whether the
read operation was successful. A value of 1 indicates success; 0 indicates end-of-file
encountered; and —1 indicates that an error occurred. Possible forms for getline are:

getline Reads next input record into $0 and splits the record into fields. NF, NR,
and FNR are set appropriately.
getline var
Reads next input record into the variable var. The record is not split into

fields (which means that the current $i values do not change). NR and FNR
are set appropriately.

getline <expr
Interprets the string value of expr to be a file name. The next record from
that file is read into $0 and split into fields. NF is set appropriately.

getline var <expr
Interprets the string value of expr to be a file name, and reads the next record
from that file into the variable var. The record is not split into fields.

expr | getline
Interprets the string value of expr as a command line to be executed. Output
from this command is piped into getline, and read into $0 in a manner
similar to getline <expr. See the SYSTEM FUNCTION section for
additional details.

expr | getline var
Executes the string value of expr as a command and pipes the output of the
command into getline. The result is similar to getline var <expr.

close(expr)
Only a limited number of files and pipes can be open at one time. This
function will close open files or pipes. The expr must be one that came

before ‘I’ or after ‘>’ in getline, or after ‘>’, *>>’, or ‘I’ in print or printf as
described in the Output section. By closing files and pipes that are no
longer needed, you can use any number of files and pipes in the course of
executing a nawk program.

Built-In Arithmetic Functions
int(expr)
Returns the integer part of the numeric value of expr. If (expr) is omitted, the

integer part of $0 is returned.
exp(expr), log(expr), sqrt(expr)
Returns the exponential, natural logarithm, and square root of the numeric
value of expr. If (expr) is omitted, $0 is used.

sin(expr), cos(expr)
Returns the sine and cosine of the numeric value of expr (interpreted as an
angle in radians).

atan2(exprl, expr2)

1-452 Commands

nawk (1)
Returns the arctangent of exprl/expr2 in the range of -t through 7.
rand()

Returns a random floating-point number in the range O through 1.
srand(expr)

Sets the seed of the rand function to the integer value of expr. If (expr) is
omitted, nawk sets a default seed (which is the same each time nawk is
invoked).

Built-In String Functions
len = length(expr)

Returns the number of characters in the string value of expr. If (expr) is
omitted, $0 is used.

n = split(string, array, regexp)

Splits the string into fields. The expression regexp is a regular expression
giving the field separator string for the purposes of this operation. The
elements of array are assigned the separated fields in order; subscripts for
array begin at 1. All other elements of array are discarded. The result of
split is the number of fields into which string was divided (which is also
the maximum subscript for array). Note that regexp divides the record in
the same way that the FS field separator string does. If regexp is omitted
in the call to split, the current value of FS will be used.

str = substr(string, m, len)

Returns the substring of string that begins in position m and is at most len
characters long. The first character of the string has m equal to one. If len
is omitted, the rest of string is returned.

pos = index(sl, s2)

Returns the position of the first occurrence of string s2 in string s/; if 52 is
not found in s/, index returns zero.

pos = match(string, regexp)

Searches string for the first substring matching the regular expression
regexp, and returns an integer giving the position of this substring. If no
such substring is found, match returns zero. The built-in variable
RSTART is set to pos and the built-in variable RLENGTH is set to the
length of the matched string. These are both set to zero if there is no
match. The regexp can be enclosed in slashes or given as a string.

n = gsub(regexp, repl, string)

globally replaces all substrings of string that match the regular expression
regexp, and replaces the substring with the string repl. If string is
omitted, the current record ($0) is used. The notation gsub returns the
number of substrings that were replaced or zero if no match occurred.

n = sub(regexp, repl, string)

Works like gsub except that at most one match and substitution is
attempted.

str = sprintf(fmt, expr, expr...)

Formats the expression list expr, expr, ... using specifications from the
string fmt, then returns the formatted string. The fm¢ string consists of
conversion specifications which convert and add the next expr to the
Commands 1-453

nawk (1)
string, and ordinary characters which are simply added to the string.
Conversion specifications have the form
$[-1[x1[.ylc

where

—

left justifies the field

1s the minimum field width

is the precision

1s the conversion character

In a string, the precision is the maximum number of characters to be
printed from the string; in a number, the precision is the number of digits
to be printed to the right of the decimal point in a floating point value. If
x oryis ‘*’ (asterisk), the minimum field width or precision will be the
value of the next expr in the call to sprintf.

Lboa
o He X O Q

The conversion character c is one of following:

Decimal integer
Unsigned octal integer
Unsigned hexadecimal integer
Unsigned decimal integer
Floating point
Floating point (scientific notation)
The shorter of e and f (suppresses non-significant zeros)
Single character of an integer value

String

n = ord(expr)
Returns the integer value of first character in the string value of expr.

This is useful in conjunction with ‘%c’ in sprintf.
str = tolower(expr)

Converts all letters in the string value of expr into lower case, and returns
the result. If expr is omitted, $0 is used.
str = toupper(expr)

Converts all letters in the string value of expr into upper case, and returns
the result. If expr is omitted, $0 is used.

The System Function
status = system(expr)

Executes the string value of expr as a command. For example,
system("tail

$1)

calls the tail(l) command, using the string value of $1 as the file that
tail should examine. See the Restrictions section for a discussion of
the execution of the command.

1-454 Commands

nawk(1)

User-Defined Functions
You can define your own functions using the form
function name (parameter-list)

{

statements

}

A function definition can appear in the place of a pattern {action} rule. The
parameter-list contains any number of normal (scalar) and array variables separated
by commas. When a function is called, scalar arguments are passed by value, and
array arguments are passed by reference. The names specified in the parameter-list
are local to the function; all other names used in the function are are global. Local
scalar variables can be defined by adding them to the end of the parameter list.
These extra parameters are not used in any call to the function.

A function returns to its caller either when the final statement in the function is
executed, or when an explicit return statement is executed.

Patterns and Actions

A pattern is a regular expression, a special pattern, a pattern range, or any arithmetic
expression.

BEGIN is a special pattern used to label actions that should be performed before any
input records have been read. END is a special pattern used to label actions that
should be performed after all input records have been read.
A pattern range is given as
patternl , pattern2

This matches all lines from one that matches patternl to one that matches pattern2,
inclusive.

If a pattern is omitted, or if the numeric value of the pattern is non-zero (true), the

resulting action is executed for the line.

An action is a series of statements terminated by semicolons, new-lines, or closing
braces. A condition is any expression; a non-zero value is considered true, and a zero
value is considered false. A statement is one of the following:
expression
if

(condition)
statement

[else

while

statement ]
(condition)
Statement

do
Statement

while

for

(condition)

(expressionl;

condition;

expression2)

statement

The for statement is equivalent to:
expressionl
while (condition)

{

Commands 1-455

nawk (1)
statement

expression2

}

The for statement can also have the form
for

(i in array)
statement

The statement is executed once for each element in array; on each repetition, the
variable i will contain the name of a subscript of array, running through all the
subscripts in an arbitrary order. If array is multi-dimensional (has multiple
subscripts), i will be expressed as a single string with the SUBSEP character
separating the subscripts. The following simple statements are supported:
break

Exits a for or a while loop immediately.

continue

Stops the current iteration of a for or while loop and begins the next
iteration (if there is one).
next

Terminates any processing for the current input record and immediately

starts processing the next input record. Processing for the next record will
begin with the first appropriate rule.

exit[ (expr) ]
Immediately goes to the END action if it exists; if there is no END action,
or if nawk is already executing the END action, the nawk program
terminates. The exit status of the program is set to the numeric value of
expr. If (expr) is omitted, the exit status is 0.
return [expr]
Returns from the execution of a function. If an expr is specified, the value
of the expression is returned as the result of the function. Otherwise, the
function result is undefined.
delete arrayli]
Deletes element i from the given array.
print expr, expr, ...

Described below.
printf fmt, expr, expr, ...
Described below.

Output
The print and printf statements write to the standard output. Output can be
redirected to a file or pipe as described below.
If >expr is added to a print or printf statement, the string value of expr is taken to
be a file name, and output is written to that file. Similarly, if >RI >> expr is added,
output will be appended to the current contents of the file. The distinction between
‘>’ and “>>’ is only important for the first print to the file expr.

Subsequent outputs

to an already open file will append to what is there already.
In order to eliminate ambiguities, statements such as
print

> b

are syntactically illegal. Parentheses must be used to resolve the ambiguity.

1-456 Commands

nawk (1)
If lexpr is added to a print or printf statement, the string value of expr is taken to be
an executable command. The command is executed with the output from the
statement piped as input into the command.

As noted earlier, only a limited number of files and pipes can be open at any time.
To avoid going over the limit, you should use the close function to close files and
pipes when they are no longer needed.
The print statement prints its arguments with only simple formatting. If it has no
arguments, the current input record is printed in its entirety. The output record
separator ORS is added to the end of the output produced by each print statement;
when arguments in the print statement are separated by commas, the corresponding
output values will be separated by the output field separator OFS. ORS and OFS are
built-in variables whose values can be changed by assigning them strings. The
default output record separator is a new-line and the default output field separator is a
space. The format of numbers output by print is given by the string OFMT. By
default, the value is ‘%.6g’; this can be changed by assigning OFMT a different
string value.

The printf statement formats its arguments using the fm¢ argument. Formatting is
the same as for the built-in function sprintf. Unlike print, printf does not add
output separators automatically. This gives the program more precise control of the
output.

Restrictions
The longest input record is restricted to 20,000 bytes and the maximum number of
fields supported is 4000. The length of the string produced by sprintf is limited to
1024 bytes.

The ord function may not be recognized by other versions of awk. The toupper and
tolower functions and the ENVIRON array variable are found in the Bell Labs
version of awk; this version is a superset of ‘New AWK’ as described in The AWK
Programming Language by Aho, Weinberger, and Kernighan.
The shell that is used by the functions
getline

printf

system

and the return value of the system function is described in system(3).

Examples
The following example outputs the contents of the file input1 with line numbers

prepended to each line:
nawk

’{print NR ":"

$0}’

inputl

The following is an example using var=value on the command line:
nawk

’{print NR SEP

$0}’

SEP=":"

inputl

The nawk program script can also be read from a file as in the command line:
nawk -f addline.nawk inputl

This example produces the same output as the previous example when the file
addline.nawk contains
{print NR ":"

$0}

Commands 1-457

nawk (1)

The following program appends all input lines starting with ‘January’ to the file jan

(which can already exist or not), and all lines starting with ‘February’ or ‘March’ to
the file febmar:
/*January/ {print >> "jan"}
/*February|*March/ {print >>

"febmar"}

This program prints the total and average for the last column of each input line:
{s

END

$NF}

{print

"sum is",

"average

is",

s/NR}

The following program interchanges the first and second fields of input lines:
{
tmp =

$1 = $2

$2 = tmp
print

}

The following example inserts line numbers so that output lines are left-aligned:
{printf

"%-6d:

%s\n",

NR,

$0}

This example prints input records in reverse order (assuming sufficient memory):
{
a[NR]

= $0

index using record number

}
END

{

for

= NR;
print

1i>0; -—1)
al[i]

}

The next program determines the number of lines starting with the same first field:
{
++a[$1]

array

indexed

using

the

first

field

}
END

{

note

for

output
in

will be

in undefined order

ali],

"lines

start

with",

}

The following program can be used to determine the number of lines in each input
file:
{
++a [FILENAME]

}
END

{

for

(file

in a)

(a[file]

file,

"has

file,

"has",

line"

else

1-458 Commands

a[file],

"lines"

nawk (1)
This program illustrates how a two dimensional array can be used in nawk. Assume
the first field contains a product number, the second field contains a month number,
and the third field contains a quantity (bought, sold, or whatever). The program
generates a table of products versus month.
BEGIN

{

{NUMPROD = 5}

array[$1,$2]

}
END

+= $3

{

print "\t Jan\t Feb\tMarch\tAprillt May\t" \
"June\tJuly\t Aug\tSept\t Oct\t Nov\t Dec"
for

(prod = 1; prod <= NUMPROD;
printf "$-7s",

prod++)

{

"prod#" prod

{
(month = 1; month <= 12; month++)
printf "\t%5d", arrayl(prod,month]

for
}

printf

"\n"

}

As this program reads in each line of input, it reports whether the line matches a

pre-determined value:

() {
function randint
return (int ((rand()+1)*10)})

}
BEGIN

{

prize[randint (),randint ()] = "$100";
()] = "$10";
ndint
(), randint
prize([ra
prize[l,1]

= "the booby prize"

}
if

(($1,$2)

in prize)

printf "You have won %s!\n",

prize[$l,$2]

}
END

This example prints lines whose first and last fields are the same, reversing the order
of the fields:
$1==$NF

{

for

(i = NF; i > 0; --i)
printf "%s", $i (i>1

? OFS

ORS)

}

The following program prints the input files from the command line. The infiles
function first empties the array passed to it, and then fills the array. Notice that the
extra parameter i of infiles is a local variable.
(£,
function infiles
for (i in f)
delete

for

{

f[i]

(i = 1; 1 < ARGC; i++)
if (index (ARGV[i],"=")
f[i]

BEGIN

== 0)

= ARGV[i]

{
infiles
(a)

for

in a)
print

al[il]

Commands 1-459

nawk (1)
exit

}

This example is the standard recursive factorial function:
function

fact (num)

(num

{

return

num *

else
fact (num

}
{

factorial

fact($0)

}

The last program illustrates the use of getline with a pipe. Here, getline sets the
current record from the output of the wc(1) command. The program prints the
number of words in each input file.
function

words (file,

string)

string =

"wc

string

getline

{

close (string)

return
BEGIN

($2)

{

for

(i=1;
fn

i<ARGC;

i++)

{

= ARGV([i]

printf

"There

are

words (fn),

£n

%d words

%s.",

See Also
ed(1), grep(1), sed(1), ex(1), system(3), ascii(7),
"Awk — A Pattern Scanning and Processing Language" ULTRIX Supplementary
Documents, Vol. Il: Programmer

1-460 Commands

netstat(1)

Name
netstat — show network status

Syntax

netstat [ -Aan | [ —f address_family 1[ system ][ core ]
netstat [ —himnrs ] [ -f address_family 1[ system ] [ core ]
netstat [ —n ][ -1 interface 1 interval [ system ][ core ]

Description

The net stat command displays the contents of network-related data structures
symbolically. Depending on the options for the information presented, there are a

number of output formats. The first form of the command displays a list of active
sockets for each protocol. The second form presents the contents of one of the other
network data structures according to the option selected. The third form, with an
interval specified, continuously displays the information regarding packet traffic on
the configured network interfaces. If no options are specified, netstat displays the
state of all active sockets from those using any of the protocols listed in
/etc/protocols.

The arguments, system and core allow substitutes for the defaults /vmunix and
/dev/kmem.

If an interval is specified, net stat display the information regarding packet traffic
on the configured network interfaces continuously, pausing interval seconds before
refreshing the screen.

There are a number of display formats, depending on the information presented. The
default display, for active sockets, shows the local and remote addresses, send and
receive queue sizes (in bytes), protocol, and, optionally, the internal state of the
protocol.

Address formats are either of the form host.port or network.port, if a socket’s address
specifies a network but no specific host address. When known, the host and network
addresses are displayed symbolically according to the data bases /etc/hosts and
/etc/networks, respectively. If a symbolic name for an address is unknown, or
if the —n option is specified, the address is printed in the Internet dot format. Refer
to inet(3n) for more information regarding this format. Unspecified, or wildcard,
addresses and ports appear as an asterisk (*).

The interface display provides a table of cumulative statistics regarding packets

transferred, errors, and collisions. The network address (currently Internet specific)

of the interface and the maximum transmission unit (mtu) are also displayed.
The routing table display indicates the available routes and their status. Each route
consists of a destination host or network and a gateway to use in forwarding packets.
The flags field shows the state of the route (for example, U if up), whether the route

is to a gateway (G), and whether the route was created dynamically by a redirect (D).
Direct routes are created for each interface attached to the local host. The gateway
field for such entries shows the address of the outgoing interface. The refcnt field
gives the current number of active uses of the route. Connection oriented protocols

normally hold on to a single route for the duration of a connection, while
connectionless protocols obtain a route while sending to the same destination. The
use field provides a count of the number of packets sent using that route. The

interface entry indicates the network interface utilized for the route.

Commands 1-461

netstat(1)

When netstat is invoked with an interval argument, it displays a running count of
statistics related to network interfaces. This display consists of a column for the
primary interface (the first interface found during autoconfiguration), and a column
summarizing information for all interfaces. The primary interface may be replaced
with another interface with the —I option. The first line of each screen of information
contains a summary since the system was last rebooted. Subsequent lines of output

show values accumulated over the preceding interval.

Options
-A

Displays the address of any associated protocol control
blocks; used for debugging.

-a

Displays the information for all sockets. Normally sockets
used by server processes are not shown.

—f address_family

Limits statistics or address control block reports to those of

the specified address family. Recognized address families are

inet, for AF_INET, and unix, for AF_UNIX.

-h

Displays the state of the IMP host table.

~I interface

Shows information only about this interface. Used with an
interval displayed below.

Displays status information for autoconfigured interfaces .
Interfaces statically configured into a system, but not located
at boot time are not shown.
Displays information for the memory management routines
The network manages a private share of memory.
Displays network addresses as numbers. Normally
netstat interprets addresses and attempts to display them
symbolically.
-r

Displays the routing tables. When —s is also present, shows
routing statistics instead.

-S

Displays per-protocol statistics.

-t

Displays time until interface watchdog routine starts up
(used only in conjunction with —i option).

See Also
jostat(1), vmstat(1), hosts(S), networks(5), protocols(5), services(5), trpt(8c)

1-462 Commands

newaliases (1)

Name
newaliases — rebuild the data base for the mail aliases file

Syntax
newaliases

Description

The newaliases command rebuilds the random access data base for the mail
aliases file /usr/lib/aliases. It must be run each time
Jusr/lib/aliases is changed in order for the change to take effect.

See Also

pi(1), pxp(1), pxref(1)

"Berkeley Pascal User’s Manual," ULTRIX Supplementary Documents,
Vol. II:Programmer

1-504 Commands

pdx (1)
Name
pdx — pascal debugger

Syntax

pdx [~r] [ objfile]
Description
The pdx command is a tool for source level debugging and execution of Pascal

programs. The objfile is an object file produced by the Pascal translator pi(1). If no
objfile is specified, pdx looks for a file named ‘‘obj’’ in the current directory. The
object file contains a symbol table which includes the name of the all the source files
translated by pi to create it. These files are available for perusal while using the
debugger.

If the file .pdxinit exists in the current directory, then the debugger commands in it
are executed.

The —r option causes the objfile to be executed immediately; if it terminates
successfully pdx exits. Otherwise it reports the reason for termination and offers the
user the option of entering the debugger or simply letting px continue with a
traceback. If —r is not specified, pdx just prompts and waits for a command.
The commands are:

run [args] [< filename] [> filename]
Start executing objfile, passing args as command line arguments; < or >

can be used to redirect input or output in the usual manner.

trace [in procedurelfunction] [if condition]
trace source-line-number [if condition]

trace procedurelfunction [in procedure/function] [if condition]

trace expression at source-line-number [if condition]
trace variable [in procedure/function] [if condition]
Have tracing information printed when the program is executed. A

number is associated with the command that is used to turn the tracing off
(see the delete command).

The first argument describes what is to be traced. If it is a source-linenumber, then the line is printed immediately prior to being executed.
Source line numbers in a file other than the current one must be preceded
by the name of the file and a colon, for example, ‘‘mumble.p:17°".

If the argument is a procedure or function name then every time it is
called, information is printed telling what routine called it, from what
source line it was called, and what parameters were passed to it. In
addition, its return is noted, and if it’s a function then the value it is

returning is also printed.

If the argument is an expression with an at clause then the value of the
expression is printed whenever the identified source line is reached.

If the argument is a variable then the name and value of the variable is

Commands 1-505

VAX

pdx(1)
printed whenever it changes. Execution is substantially slower during this
form of tracing.

If no argument is specified then all source lines are printed before they are
executed. Execution is substantially slower during this form of tracing.
The clause ‘‘in procedure/function’’ restricts tracing information to be
printed only while executing inside the given procedure or function.

Condition is a Pascal boolean expression and is evaluated prior to printing
the tracing information,; if it is false then the information is not printed.
There 1s no restriction on the amount of information that can be traced.

stop if condition
stop at source-line-number [if condition]
stop in procedure/function [if condition]
stop variable [if condition]
Stop execution when the given line is reached, procedure or function
called, variable changed, or condition true.
delete command-number
The trace or stop corresponding to the given number is removed. The
numbers associated with traces and stops are printed by the status

command.
status [> filename]
Print out the currently active trace and stop commands.
cont

Continue execution from where it stopped. This can only be done when
the program was stopped by an interrupt or through use of the stop
command.

step

Execute one source line.

Execute up to the next source line. The difference between this and step
is that if the line contains a call to a procedure or function the step
command will stop at the beginning of that block, while the next
command will not.

print expression [, expression ...}

Print out the values of the Pascal expressions. Variables declared in an
outer block but having the same identifier as one in the current block may
be referenced as ‘‘block-name . variable’’.
whatis identifier

Print the declaration of the given identifier.
which identifier
Print the full qualification of the given identifier, that is the outer blocks
that the identifier is associated with.
assign variable expression
Assign the value of the expression to the variable.
call procedure(parameters)
Execute the object code associated with the named procedure or function.

1-506 Commands

pdx(1)
help

Print out a synopsis of pdx commands.

gripe

Invokes a mail program to send a message to the person in charge of
pdx.

where

Print out a list of the active procedures and functions and the respective
source line where they are called.

source filename

Read pdx commands from the given filename. Especially useful when the
filename has been created by redirecting a status command from an earlier
debugging session.

dump [> filename]
Print the names and values of all active data.

list [source-line-number [, source-line-number]]
list procedure/function

List the lines in the current source file from the first line number to the
second inclusive. As in the editor ‘‘$’’ can be used to refer to the last
line. If no lines are specified, the entire file is listed. If the name of a
procedure or function is given lines n-k to n+k are listed where n is the
first statement in the procedure or function and k is small.

file [filename]

Change the current source file name to filename. If none is specified then

the current source file name is printed.
edit [filename]
edit procedurelfunction-name

Invoke an editor on filename or the current source file if none is specified.
If a procedure or function name is specified, the editor is invoked on the
file that contains it. Which editor is invoked by default depends on the
installation. The default can be overridden by setting the environment
variable EDITOR to the name of the desired editor.

Recompile the program and read in the new symbol table information.

sh command-line
Pass the command line to the shell for execution. The SHELL
environment variable determines which shell is used.

alias new-command-name old-command-name

This command makes pdx respond to new-command-name the way it
used to respond to old-command-name.

quit

Exit pdx.

The following commands deal with the program at the px instruction level rather than
source level. They are not intended for general use.

tracei [address] [if cond]
tracei [variable] [at address] [if cond]
stopi [address] [if cond]
stopi [at] [address] [if cond]
Turn on tracing or set a stop using a px machine instruction addresses.

Commands 1-507

VAX

pdx (1)
Xi address [, address]

Print the instructions starting at the first address. Instructions up to the
second address are printed.
xd address [, address]
Print in octal the specified data location(s).

Options
-r

Causes obifile to be executed immediately. Normally pdx prompts and
waits for a command.

Restrictions
The pdx command does not understand sets, and provides no information about files.

The what is command doesn’t quite work for variant records.
Unexpected results occur if a procedure invoked with the call command does a nonlocal goto.

Files
obj

Pascal object file

.pdxinit

pdx initialization file

See Also

pi(1), px(1)

1-508 Commands

pg(1)
Name
pg — file perusal filter for soft-copy terminals

Syntax
pg [-number] [-p string] [—cefs] [+linenumber] [+/pattern/] [files...]

Description
The pg command is a filter that allows the examination of files one screenful at a
time on a soft-copy terminal. When the file name is designated by a minus (-)
and/or NULL argument, the pg command reads from the standard input. Each
screenful is followed by a prompt. If the user types a carriage return, another page is
displayed.

This command is different from previous paginators because it allows you to back up
and review material that has already passed.

In order to determine terminal attributes, pg scans the terminfo(5) data base for
the terminal type specified by the environment variable TERM. If TERM is not
defined, the terminal is assumed to be a dumb terminal. The pg command takes
responses that can be divided into three categories: those causing further perusal,
those that search, and those that modify the perusal environment.
Commands causing further perusal normally take a preceding address, which is an
optionally signed number indicating the point from which further text should be
displayed. This address is interpreted in either pages or lines depending on the
command. A signed address specifies a point relative to the current page or line, and
an unsigned address specifies an address relative to the beginning of the file. Each
command has a default address that is used if none is provided.
The perusal commands and their defaults are as follows:
(+1)<newline> or <blank>

Causes one page to be displayed. The address is specified in

pages.

+1D1

Causes pg to simulate scrolling the screen, forward or
backward, the number of lines specified when used with a
relative address. With an absolute address this command
prints a screenful beginning at the specified line.

(+1)d or AD

Simulates scrolling half a screen forward or backward.

The following perusal commands take no address:

.or AL

Causes the current page of text to be redisplayed.

Displays the last windowful in the file. Use with caution
when the input is a pipe.

Commands 1-509

pg(1)
The following commands are available for searching for text patterns in the text. The
regular expressions described in ed(1) are available. They must always be
terminated by a <newline>, even if the —n option is specified.

ilpattern/

Searches forward for the ith (default i=1) occurrence of
pattern. Searching begins immediately after the current page
and continues to the end of the current file, without wraparound.

iApattern?
i ?pattern?
Searches backwards for the ith (default i=1) occurrence of pattern.
Searching begins immediately before the current page and continues to the
beginning of the current file, without wrap-around. The circumflex (#)
notation is useful for Adds 100 terminals which do not handle the question
mark (?) properly.

After searching, pg normally displays the line found at the top of the screen. This
can be modified by appending m or b to the search command to leave the line found
in the middle or at the bottom of the window from now on. The suffix t can be used
to restore the original situation.
The user of pg can modify the environment of perusal with the following commands:

in
i

Begins perusing the ith next file in the command line. The i
is an unsigned number. Default value is 1.
Begins perusing the ith previous file in the command line. i
is an unsigned number. Default is 1.

Displays another window of text. If i is present, sets the
window size to i.

s filename

Saves the input in the named file. Only the current file
being perused is saved. The white space between the s and
filename is optional. This command must always be
terminated by a <newline>, even if the —n option is
specified.

Helps by displaying an abbreviated summary of available
commands.

qor Q

Quits pg.

Ycommand

The command is passed to the shell, whose name is taken
from the SHELL environment variable. If this is not
available, the default shell is used. This command must
always be terminated by a <newline>, even if the —n option
is specified.

At any time when output is being sent to the terminal, the user can hit the quit key
(normally control-\) or the interrupt (break) key. This causes pg to stop sending
output and to display the prompt. The user may then enter one of the above
commands in the normal manner. Unfortunately, some output is lost when this is
done, because any characters waiting in the terminal’s output queue are flushed when
the quit signal occurs.

1-510 Commands

pg(1)
If the standard output is not a terminal, then pg acts just like cat(1), except that a
header is printed before each file (if there is more than one).

Options
The command line options are:

—number

Specifies the size (in lines) of the window that pg is to use instead
of the default. (On a terminal containing 24 lines, the default
window size is 23).

-p string

Causes pg to use st ring as the prompt. If the prompt string
contains a %d, the first occurrence of %d in the prompt is replaced
by the current page number when the prompt is issued. The
default prompt string is designated by a colon (:).
Homes the cursor and clears the screen before displaying each

page. This option is ignored if clear_screen is not defined for this
terminal type in the terminfo(5) data base.
Causes pg not to pause at the end of each file.

—f

Inhibits pg from splitting lines. Normally, pg splits lines longer
than the screen width, but some sequences of characters in the text

being displayed (for example, escape sequences for underlining)
generate undesirable results. The —f option prevents the splitting
of these sequences.
Causes pg to print all messages and prompts in standout mode

-S

(usually inverse video).
+linenumber

Starts up at linenumber.

+/pattern/

Starts up at the first line containing the regular expression pattern.

Examples
The following example shows how the pg command is used reading system news:
news

-p

"(Page

%d):"

Notes
While waiting for terminal input, pg responds to BREAK, DEL and the circumflex
(M) by terminating execution. Between prompts, however, these signals interrupt pg
command’s current task and place the user in prompt mode. These should be used
with caution when input is being read from a pipe, since an interrupt is likely to

terminate the other commands in the pipeline.

Restrictions
Terminal tabs must be set every eight positions.
Using pg as a filter with another command changes the terminal I/O options. For
example, crypt(1) terminal settings may not be restored correctly.

Commands 1-511

pg(1)
Files
/usr/lib/terminfo/*
Terminal information data base

/tmp/pg*

Temporary file when input is from a pipe

See Also
crypt(1), ed(1), grep(1), terminfo(5)

1-512 Commands

pi(1)

Name
pi — Pascal interpreter code translator

Syntax
pi [ options] [-i name...] name.p

Description
The pi command translates the program in the file name.p leaving interpreter code in
the file obj in the current directory. The interpreter code can be executed using px.
The pix command performs the functions of pi and px for ‘load and go’ Pascal.

Options
The following flags are interpreted by pi. The associated options can also be
controlled in comments within the program as described in the "Berkeley Pascal
User’s Manual."
-b

Block buffers the file output.

Enables listing for specified procedures and functions and while processing
specified include files.

Creates a program listing while translating source.

-~n

Begins each listed include file on a new page with a banner line.

-p

Suppresses control flow backtrace on error; suppresses statement limit
counting.

-S

Accepts standard Pascal only; non-standard constructs cause warning
diagnostics.

Suppresses runtime tests of subrange variables and treat; treats assert

‘statements as comments.

-u

Runs in card image mode; only the first 72 characters of input lines are used.

-w

Suppresses all warning diagnostics.

-Z

Enables execution profiling with pxp by generating statement counters, and
arranging for the creation of the profile data file pmon.out when the resulting
object is executed.

Restrictions
The keyword packed is recognized but has no effect.
When include files are present, diagnostics relating to the last procedure in one file
may appear after the beginning of the listing of the next.

Commands 1-513

VAX

pi(1)
Diagnostics
For a basic explanation type:
pi

In the diagnostic output of the translator, lines containing syntax errors are listed with
a flag indicating the point of error. Diagnostic messages indicate the action which

the recovery mechanism took in order to be able to continue parsing. Some
diagnostics indicate only that the input is ‘malformed.” This occurs if the recovery
can find no simple correction to make the input syntactically valid.

Semantic error diagnostics indicate a line in the source text near the point of error.
Some errors evoke more than one diagnostic to help pinpoint the error; the follow-up

messages begin with an ellipsis °...".

The first character of each error message indicates its class:
E
e

w
s

Fatal error; no code is generated.
Non-fatal error.

Warning — a potential problem.
Non-standard Pascal construct warning.

If a severe error occurs which inhibits further processing, the translator gives a

diagnostic and then ‘QUIT’.

Files
file.p
file.1

fusr/lib/pi3.*strings
fusr/lib/how_pi*
obj

input file
include file(s)
text of the error messages
basic usage explanation
interpreter code output

See Also

pix(1), px(1), pxp(1), pxref(1)

"Berkeley Pascal User’s Manual," ULTRIX Supplementary Documents,

Vol. II: Programmer

1-514 Commands

pick(1mh)

Name
pick — select messages by content

Syntax
pick [+folder] [msgs] [-and ...] [-or ...] [-not ...] [-Ibrace ... —=rbrace] [—cc pattern]

[-date pattern] [-from pattern] [-search pattern] [-subject pattern] [-to pattern]
[-—othercomponent pattern] [-after date] [-before date] [-datefield field]
[-sequence name ...] [—public] [-nopublic] [-zero] [-nozero] [~list] [-nolist]

[-help]

Description
Pick lets you search messages in a folder on a diverse range of search criteria.
You can search the mail headers or the text of some or all of the messages within a

folder for the specified criteria. You can use pattern matching or date constraint
operations. You can define the messages found as a sequence or you can use the
results directly. The following example shows pick identifying all the mail in the
current folder that was sent by Christine.
% pick

—from christine

3
8

The search of the mail header fields that has just been performed is case insensitive.
Therefore in the previous example, pick would find messages that were from
Christine as well as messages that were from christine. However the full -search
option is not case insensitive. The way in which the —search option works is
described later in this reference page.

Options
You can search on the contents of any known mail header field by specifying the

header field as a ~option.
To:,

cc:,

Date:,

The mail header fields that pick knows about are

From:, or Subject.:.

If you want to search on some other mail header field, you can do this by using the
— — component pattern option. If you use this option, you must precede the mail
header field with two minus signs. The following example shows pick being used
to search on the reply-to: field.
% pick

--reply-to

Scott

If you want to search the entire message, and not just the message header, you can do

this using the —search option. The —search option is a modified grep(l). As
such it gives full regular expression capabilities (see ed(1)) within pattern matching.
Pattern matching is performed on a per-line basis. Within the header of the message,
each component is treated as one long line, but in the body, each line is separate.
Lower-case letters in the search pattern will match either lower or upper case in the
message, while upper case will match only upper case.

Commands

1-515

pick (1mh)
The following example shows a pick command that will search all messages in the
current folder for the word strawberries.
%

pick -search

"strawberries"

2
4

You can specify a folder other than the current folder using the +foldername
option. Also, if you do not want to search all messages within the specified folder,
you can specify more than one message or a range of messages using the message
numbers. In the following example pick searches messages 10-20 in the +sent
folder for messages that were sent to Kafka.
% pick +sent 10-20 -to Kafka
pick: no messages match specification

You can define a sequence name in which pick can store the details of the messages
found. You can manipulate these sequences with any of the MH commands that will
take the msgs argument.

A sequence name should always begin with a letter and should not contain any nonalphanumeric characters such as punctuation marks. The following example shows
the creation of a sequence called Jack.
% pick —-from Jack -sequence Jack
3

hits

Whenever pick processes a —sequence name, it calls the —nolist option. This
suppresses the list of messages meeting the search criteria that pick normally
generates. Instead pick indicates how many records met the search criteria.
pick normally zeros the sequence before adding to it. This means that any
messages that are already in the defined sequence will be lost. If you want to save
the messages that are already in the defined sequence, you can do so by specifying
the —-nozero option. In this case the new messages will be added to the existing
messages and numbered accordingly.

If the messages that make up a message sequence are read only, the message
sequence that you create will not be accessible to other MH users. If you want to
change this you can do so with the ~-public and —-nopublic switches. You can
use the —nopublic switch to ensure that the sequence that you create is only
accessible to yourself.

In addition to this, you can also combine the output of pick directly with any MH
command. In order to do this you need to encase the pick command, and its
associated options and arguments, inside single back quotes (‘ ¢). This technique is
known as back quoting and is familiar to most ULTRIX users. You should consult
your ULTRIX shell Reference Pages for more details. The following example would
give you a listing of all the mail sent to you from Jones. See scan(1mbh) for details
of the listing that would be produced.
% scan

‘pick —from jones*

If pick finds that there is no mail from Jones, it will output the illegal character 0.
This will cause the MH command, that was going to process the output from the
pick operation, to fail gracefully.

Independent of any pattern-matching operations requested, the switches ~after date
or ~before date may also be used to introduce date/time constraints on all of the
messages. By default, the Date: field is consulted. However you can specify an
1-516 Commands

pick(1mh)
alternative date field, such as Delivery-Date:, by using the ~datefield field
option. You must define the ~datefield before you use the —after or
-before switch it applies to. You must place the arguments to the —after or
-before switches inside double-quotes ("

The following example shows pick searching for all messages sent to Holloway
since 10th June.
% pick -to holloway -after "10 Jun 88"
19

Pick will actually parse the date fields in each of the specified messages and
compare them to the date/time specified by the ~after and ~before switches. If
—after is given, then only those messages whose Date: field value is
chronologically after the date specified will be examined. The -before switch
specifies the complementary action.

Both the —after and -before switches take legal RFC 822-style date
specifications as arguments. pick will assume certain missing fields so that the
entire date need not be specified. These fields are (in order of defaulting): timezone,
time and timezone, date, date and timezone. All defaults are taken from the current
date, time, and timezone.

In addition to RFC 822-style dates, pick will also recognize any of the days of the
week Sunday, Monday, and so on), and the special dates today, yesterday,
and tomorrow. All days of the week refer to a day in the past. Therefore pick
interprets Saturday as last Saturday and not this Saturday. Finally, in addition to
these special specifications, you can also direct pick to start its search a number of
days ago. The following example searches for messages sent about strawberries in
the last ten days.
% pick -subject:

strawberries -10

The pick command also supports complex boolean operations on the searching
primitives with the —and, -or, —-not , and -lbrace ... -rbrace switches.
For example,
% pick -after yesterday —and —lbrace -from freida

-or -from fear -rbrace

identifies messages recently sent by frieda or fear.

The matching primitives take precedence over the —not switch, which in turn takes
precedence over —and which in turn takes precedence over —or.
You can override the default precedence with the -1brace and —rbrace switches.
These act just like opening and closing parentheses in logical expressions.

Restrictions
The sequence name, punctuation and message list must not exceed 1024 characters.
In practice, this gives a reasonable limit of approximately 200 non-consecutive
messages in a sequence.

Commands 1-517

pick (1mh)

Files
$HOME/.mh_profile = The user profile

Profile Components
Path:

To determine your MH directory

Current—Folder:

To find the default current folder

See Also
ed(1), grep(1), inc(1mh), mark(1mh)

1-518 Commands

pix(1)

Name
pix — Pascal interpreter and executor

Syntax
pix [-blnpstuwz] [-i name...] name.p [ argument...]

Description
The pix command is a ‘load and go’ version of Pascal which combines the functions
of the interpreter code translator pi and the executor px. It uses pi to translate the
program in the file name.p and, if there were no fatal errors during translation, causes
the resulting interpreter code to be executed by px with the specified arguments. A
temporary file is used for the object code. The file obj is neither created nor
destroyed.

Options
-b

Block buffers the output.

~iname

Enables the listing for any specified procedures and functions, and while
processing any specified include files.

-1

Creates a program listing while translating source.

-n

Begins each listed include file on a new page and with a banner line.

-p

Suppresses control flow backtraces on error.

-S

Accepts standard Pascal only.

-t

Suppresses runtime test of subrange variables.

-u

Runs in card image mode.

-w

Suppresses all warning diagnostics.

—Z

Enables execution profiling.

Files
[usr/ucb/pi
[usr/ucb/px

/tmp/pix*

[usr/lib/how_pix

Pascal translator
Pascal executor

temporary

basic explanation

See Also

graph(1g), plot(3x), plot(5)

1-524 Commands

pmerge(1)

Name
pmerge — pascal file merger

Syntax
pmerge name.p...

Description
The pmerge command assembles the named Pascal files into a single standard
Pascal program. The resulting program is listed on the standard output. It is
intended to be used to merge a collection of separately compiled modules so that they
can be run through pi, or exported to other sites.

Restrictions
Very minimal error checking is done, so incorrect programs will produce
unpredictable results. Block comments should be placed after the keyword to which
they refer or they are likely to end up in bizarre places. -

Files
fust/tmp/MG*

default temporary files

See Also
pe(1), pi(l),
Auxiliary documentation "Berkeley Pascal User’s Manual," ULTRIX Supplementary
Documents Vol. II:Programmer

Commands 1-525

pr(1)
Name
pr — print files

Syntax
pr [ options ] [ files ]

Description
The pr command prints the named files on the standard output. If file is designated
by a minus sign (-), or if no files are specified the pr command assumes standard
input. By default, the listing is separated into pages, each headed by the page
number, a date and time, and the name of the file.
By default, columns are of equal width, separated by at least one space. Lines that
do not fit are truncated. However, if the —s option is used, lines are not truncated and
columns are separated by the separation character.
If the standard output is associated with a terminal, error messages are withheld until
pr has finished printing.

Options
The following options can be used singly or in combination:
Prints multi-column output across the page.
Prints blank headers.

Double-spaces the output.

Expands input tabs to character positions k+1, 2xk+1, 3xk+1,... n*k+1. If k
is 0 or is omitted, tabs are set at every eighth position. Tab characters in
the input are expanded into the appropriate number of spaces. The default
for ¢ (any non-digit character) is the tab character; therefore, if c is given, it
is treated as the input tab character.
Uses form-feed character for new pages. The default is to use a sequence
of line-feeds. The -f option causes the pr command to pause before
beginning the first page if the standard output is associated with a terminal.

Uses the next argument as the header to be printed instead of the file name.
Replaces white space in output by inserting tabs to character positions k+1,
2%k+1, 3%k+1,..n¥k+1. If k is O or is omitted, tabs are set at every eighth
position. The default for ¢ (any non-digit character) is the tab character;
therefore, if ¢ is given, it is treated as the input tab character.
+k

Begins printing with page k (default is 1).

-k

Produces k-column output (default is 1). The —e and —i options are
assumed for multi-column output.

-1k

Sets the length of a page to k lines. The default is 66 lines.
Merges and prints all files simultaneously, one per column (overrides the
—k, and —a options).

-nck

1-526 Commands

Numbers lines. The default for k is 20. The number occupies the first k+1

pr(1)
character positions of each column of normal output or each line of -m
output. If ¢, which is any non-digit character is given, it is appended to the
line number to separate it from whatever follows. The default for ¢ is a
tab.

Offsets each line by k character positions (default is 0). The number of
character positions per line is the sum of the width and offset.
Pauses before beginning each page if the output is directed to a terminal.
The pr command rings the bell at the terminal and awaits a carriage return.
Suppresses diagnostic reports on failure to open files.

Separates columns by the single character ¢ instead of by the appropriate

number of spaces (default for c is a tab).

Suppresses the five-line identifying header and the five-line trailer normally
supplied for each page. The -t option causes the pr command to quit
printing after the last line of each file without spacing to the end of the
page.

-wk

Sets the width of a line to k character positions. The default is 72 for
equal-width multi-column output; otherwise there is no limit.

Examples
Print filel and file2 as a double-spaced, three-column listing with the heading: file
list.
pr

-3dh

"file

list"

filel

file2

Write filel on file2, expanding tabs to columns 10, 19, 28, 37,....
pr -e9 -t

<filel>file2

Files
[dev/tty*

to suspend messages

See Also

pi(1), pix(1)

"Berkeley Pascal User’s Manual," ULTRIX Supplementary Documents, Vol.

II:Programmer

1-552 Commands

pxp(1)

Name
pxp — Pascal execution profiler

Syntax
pxp [-acdefjnstuw_] [-23456789] [-z[name...]] name.p

Description
The pxp command can be used to obtain execution profiles of Pascal programs or as

a pretty-printer. To produce an execution profile all that is necessary is to translate
the program specifying the z option to pi or pix, to execute the program, and to
then issue the command
PXp

-z

name.p

A reformatted listing is output if none of the c, t, or z options are specified; thus
pxp old.p >

new.p

places a pretty-printed version of the program in old.p in the file new.p.

Options
The use of the following options of pxp is discussed in sections 2.6, 5.4, 5.5 and
5.10 of the Berkeley Pascal User’s Manual.
Underscores all keywords.

—d

Uses the specified number (—d) as the indentation unit. The default is 4.

—a

Displays all procedures (even those not executed).

Uses the core file in generating the profiling data.

—d

Displays all declaration parts.

—_

Eliminates include directives when reformatting a file. The include is
replaced by the reformatted contents of the specified file.

—f

Displays all parenthesized expression.

—j

Left justifies all procedures and functions.

-n

Begins a new page for each included file. In profiles, print a blank line at the
top of the page.

—s

Strips comments from the input text.

-t

Prints a table summarizing procedure and function call counts.

—u

Generates the output in card image format, using only the first 72 characters of
input lines.

—w

Suppresses all warning diagnostics.

—z

Generate an execution profile for the specified modules (next arguments). If no
name s, are given the profile is of the entire program. If a list of names is
given, then only any specified procedures or functions and the contents of any
specified include files appear in the profile.

Commands 1-553

VAX

pxp(1)

Restrictions
Does not place multiple statements per line.

Diagnostics
For a basic explanation of the pxp command, type:
PXp

Error diagnostics include ‘No profile data in file’ with the ¢ option if the z option was
not enabled to pi; ‘Not a Pascal system core file’ if the core is not from a px

execution; ‘Program and count data do not correspond’ if the program was changed
after compilation, before profiling; or if the wrong program is specified.

Files
name.p

input file

name.i

include file(s)

pmon.out

profile data
core

profile data source with —

[usr/lib/how_pxp
information on basic usage

See Also

comp(1mh), dist(1mh), forw(1mh), prompter(1mh), send(1mh), whatnow(1mh), mhformat(5mh)

Commands 1-575

reset(1)

Name
reset — reset terminal mode

Syntax
reset

Description
The reset command sets the terminal to cooked mode, turns off cbreak and raw
modes, turns on nl, and restores special characters that are undefined to their default

values. The reset command also clears the LLITOUT bit in the local mode word.
This is most useful after a program dies leaving a terminal in a funny state; you have
to type ‘‘<LF>reset<LF>’’ to get it to work then to the shell, as <CR> often doesn’t
work; often none of this will echo.
It is a good idea to follow reset with tset(l)

Restrictions
Doesn’t set tabs properly. It can’t interpret choices for interrupt and line kill
characters, so it leaves these set to the local system standards.

See Also

cd(1), echo(1sh5), login(1), printenv(1), pwd(1), sh(1), test(1sh5) dup(2), execve(2),
fork(2), pipe(2), ulimit(2), umask(2), wait(2), signal(3), a.out(5), environ(7)

Commands 1-627

shexp (1)
Name
shexp — display password expiration information for a user

Syntax
shexp [—q] [username]

Description
The command shexp is used to display a user’s password expiration information.
The specified username, or logname if no username is supplied, is converted to a

UID by searching through the passwd file. The UID is then used to look up the
user’s entry in the Auth Data Base. The password expiration information is then

printed out in ctime (3) format.
%

shexp

Expires

}
Tue

Dec

10:49:18

EST

1988

If the password has already expired the word Expires will be replaced with the word
Expired. If password expiration is disabled for the particular user in question the
output of shexp will be Never expires.

Options
—q

Instead of displaying the expiration date and time in ct ime (3) format,
shexp outputs it as three decimal numbers: the minimum password lifetime,
the maximum password lifetime, and the password modification time. All
three numbers are displayed as they are found in the auth database.

Restrictions
Only the super-user may obtain information about users with UIDs other than the real
UID of the invoking process.

Diagnostics
User not found in passwd data base.
There is no entry in /etc/passwd for the specified username.

Cannot stat auth file.
The auth database is missing (security features may not be enabled).
Insufficient privilege.
An insufficiently privileged user is asking for information about a username with a
UID different then their current real-UID.

An exit value of 0 indicates a successful operation, any other exit status indicates an
error.

Files
/etc/auth. [pag,dir]

/etc/passwd

1-628 Commands

shexp (1)
See Also
passwd(1), getauthuid(3), auth(5)
ULTRIX Security Guide for Users and Programmers

Commands 1-629

show (1mh)

Name
show — show (list) messages

Syntax
show [+folder] [msgs] [-draft] [-header] [-noheader] [-showproc program]
[-noshowproc] [switches for showproc] [-help]

Description
Use show to display the contents of the current message. You can specify
alternative messages or folders by using the <+folder> or <msgs> arguments. In
the following example, show will display the contents of message 36, in the current
folder, on the screen.
$ show 36

If a folder is given, it will become the current folder. The last message shown will
become the current message.
You can specify a number of messages or a range of messages using the <msgs>
argument. If you specify more than one message; the default showproc, more,
will prompt for a <KRETURN> prior to listing each message.

Typically, the messages are listed exactly as they are, with no reformatting. A
program named by the showproc profile component is invoked to do the listing,

and any switches not recognized by show are passed along to that program. The
default program is known as more. The more command lists each message, a page

at a time. When the end of the page is reached, more waits for a <SPACE> or

<RETURN>. If you press <RETURN>, more will print the next line. If you press

the spacebar, more prints the next screen of data. At the end of the message, more
will automatically return you to the system prompt. Press q to quit from more before
you have finished reading the message.

Options
To override the default and the showproc profile component, use the
—showproc

program switch.

In the following example, show will cause the

pr(l) program to list the current message.
$ show —showproc pr

The MH command mh1 can be used as a showproc to show messages in a more
uniform format. See mh1(1mh) for more details. If you are going to use the same
showproc all the time, it is advisable to specify it in your .mh_profile.

You

can specify any switches, that the specified show program normally takes, after the

—showproc option. If the -noshowproc option is specified, /bin/cat is used
instead of showproc.

The —~header switch tells show to display a one-line header, which contains the
folder and the message number.
If the standard output is not a terminal, no queries are made, and each file is listed
with a one-line header and two lines of separation.

1-630 Commands

show(1mh)
The command show —-draft will list the file <mh—dir>/draft if it exists.

If the profile entry Unseen-Sequence is present and non-empty, then show will
remove each of the messages shown from each sequence named by the profile entry.
This is similar to the Previous—-Sequence profile entry supported by all MH
commands which take msgs or msg arguments.

This command has the following default settings:
+folder defaults to the current folder
msgs defaults to cur
—format

-header

Restrictions
The -header switch does not work when msgs expands to more than one message.
If the showproc is mhl, then this problem can be circumvented by referencing the
messagename field in the mh1 format file.

The command show updates your context before showing the message. Hence
show may mark messages as seen before you actually see them. However, this is

generally not a problem, unless you are using the unseen messages mechanism, and
you interrupt show while it is showing unseen messages.

If showproc is mhl, then show uses a built-in mh1: it does not actually run the
mh1 program. Hence, if you define your own showproc, do not call it mhl since
show will not run it.

If more(l) is your showproc (the default), then avoid running show in the
background with only its standard output piped to another process. In the following
incorrect example, show will go into a tty input state.
$ show | print &

To avoid this problem, re-direct show’s diagnostic output as well.
For users of csh:
$ show |& print &

For users of sh:
$ show 2>&1 | print &

Files
$HOME/.mh_profile = The user profile

Profile Components
Path:
Current-Folder:

Unseen-Sequence:
showproc:

To determine the user’s MH directory
To find the default current folder

To name sequences denoting unseen messages
Program to show messages

Commands 1-631

show(1mh)

See Also
mhl(1mh), more(1), next(1mh), pick(1mh), prev(1mh), scan(1mh)

1-632 Commands

size(1)
Name
size — prints the section size of an object file

Syntax
size [-0 -d -x -A -B -V] [ filel ... filen ]

Description
The size command prints information about the text, rdata, data, sdata, bss and sbss
sections of each file. The file can be an object or an archive. If you do not specify a
file, size uses a.out as the default.

Options
The —o0, —x, and —d options print the size in octal, hexadecimal, and decimal,
respectively.

The —A and -B options specify AT&T System V style output or Berkeley (4.3BSD)
style output, respectively. The version of UNIX running at your site determines the
default. System V style, which is more verbose than Berkeley, dumps the headers of
each section. The Berkeley version prints size information for each section,
regardless of whether the file exists, and prints the total in hexadecimal and decimal.
The ~V option prints the version of size that you are using.

Commands 1-633

RISC

VAX

size (1)

Name
size — print program’s sizes

Syntax
size [ object... ]

Description
The size command prints the (decimal) number of bytes required by the text, data,
and bss portions, and their sum in hex and decimal, of each object-file argument. If

no file is specified, a.out is used.

See Also

graph(lg), plot(1g)

Commands 1-651

split(1)

Name
split — split file into smaller files

Syntax
split [-n] [ file [name]]

Description
The split command reads file and writes it in z-line pieces (default 1000), as many
as necessary, onto a set of output files. The name of the first output file is name with
aa appended, and so on lexicographically. If no output name is given, x is default.

If no input file is given, or if — is given in its stead, then the standard input file is
used.

Options
-

Uses standard input.

-n

Writes specified number of lines to each output file. Default is 1000.

1-652 Commands

stcode (1ncs)

Name
stcode — translate a hexadecimal status code value to a textual message

Syntax
stcode hex_stat_code

Description
The st code command prints the textual message associated with a hexadecimal
status code. This command is useful when a program produces a hexadecimal status
code instead of a textual message.

The stcode command processes predefined status codes. No provision is currently
made to add user-defined status codes to the error text database.

Examples
Translate the hexadecimal status code 1c010003:
# stcode 1c010003

unknown interface

(network computing system/RPC runtime)

Commands 1-653

strextract (1int)

Name
strextract — batch string extraction

Syntax
strextract [ —p patternfile 1 [ —i ignorefile ] [ —d ] [ source-program... ]

Description
The strextract command extracts text strings from source programs. This
command also writes the string it extracts to a message text file. The message text
file contains the text for each message extracted from your input source program. The
strextract command names the file by appending .msg to the name of the input
source program.

In the source-program argument, you name one or more source programs from which
you want messages extracted. The st rextract command does not extract
messages from source programs included using the #include directive. Therefore,
you might want a source program and all the source programs it includes on a single
strextract command line.

You can create a patterns file (as specified by patternfile ) to control how the
strextract command extracts text. The patterns file is divided into several
sections, each of which is identified by a keyword. The keyword must start at the
beginning of a new line, and its first character must be a dollar sign ($). Following
the identifier, you specify a number of patterns. Each pattern begins on a new line
and follows the regular expression syntax you use in the regex(3) routine. For more
information on the patterns file, see the patterns (5int) reference page.
In addition to the patterns file, you can create a file that indicates strings that

extract ignores. Each line in this ignore file contains a single string to be ignored
that follows the syntax of the regex(3) routine.
When you invoke the st rextract command, it reads the patterns file and the file
that contains strings it ignores. You can specify a patterns file and an ignore file on
the strextract command line. Otherwise, the strextract command matches
all strings and uses the default patterns file.
If strextract finds strings which match the ERROR directive in the pattern file, it
reports the strings to standard error (stderr.) but does not write the string to the

message file.
After running strextract, you can edit the message text file to remove text

strings which do not need translating before running st rmerge.
It is recommended that you use extract command as a visual front end to the
strextract command rather than running strextract directly.

Options
—-i

Ignore text strings specified in ignorefile. By default, the strextract
command searches for ignorefile in the current working directory, your home
directory, and /usr/1ib/intln.
If you omit the —1i option, strextract recognizes all strings specified in the
patterns file.

1-654 Commands

strextract (1int)
—p

Use patternfile to match strings in the input source program. By default, the

command searches for the pattern file in the current working directory, your
home directory, and finally /usr/1lib/intln.
If you omit the —p option, the strextract command uses a default patterns

file that is stored in /usr/lib/intln/patterns.
—d

Disables warnings of duplicate strings. If you omit the -d option,
strextract prints warnings of duplicate strings in your source program.

Restrictions
Given the default pattern file, you cannot cause st rextract to ignore strings in
comments that are longer than one line.
You can specify only one rewrite string for all classes of pattern matches.
The strextract command does not extract strings from files include with

#include directive. You must run the strextract commands on these files
separately.
%

strextract

-p

c_patterns

prog.c prog2.c

prog.msg

strmerge

gencat prog.cat

-p

c_patterns

nl_prog.c

nl_prog2.c

nl_prog.c

prog.c prog2.c

prog.msf prog2.msf

nl_prog2.c

-1i

In this example, the st rextract command uses the c_patterns file to
determine which strings to match. The input source programs are named prog. c

and prog2.c.
If you need to remove any of the messages or extract one of the created strings, edit
the resulting message file, prog.msg. Under no conditions should you add to this
file. Doing so could result in unpredictable behavior.

You issue the st rmerge command to replace the extracted strings with calls to the
message catalog. In response to this command, st rmerge, creates the source
message catalogs, prog.msf and prog2.ms£, and the output source programs,
nl_prog.cand nl_prog2.c.
You must edit n1_prog.c and nl_prog2.c to include the appropriate catopen
and catclose function calls.
The gencat command creates a message catalog and the cc command creates an
executable program.

See Also
intro(3int), gencat(lint), extract(lint), strmerge(lint), regex(3), catopen(3int),
patterns(Sint)
Guide to Developing International Software

Commands 1-655

strings (1)
Name
strings — print ASCII strings in program

Syntax
strings [-|a] [-0] [-number] file...

Description
The strings command looks for ascii strings in a binary file. A string is any
sequence of 4 or more printing characters ending with a newline or a null.

The st rings command is useful for identifying random object files and many other
things.

Options
—or-a
—number
-0

See Also

mail(1), uucp(1c), uusend(1c), uux(lc), uuencode(5)

Commands

1-729

uuid_gen(1ncs)
Name
uuid_gen — UUID generating program

Syntax
/etc/nes/uuid_gen [ — ] [ =C ] [ —version ]

Description
The uuid gen program generates Universal Unique Identifiers (UUIDs). Without
options, it generates a character-string representation of a UUID. The —c option
enables you to generate a template for Network Interface Definition Language
(NIDL) files. The —C option enables you to generate source-code representations of
UUIDs, suitable for initializing variables of type uuid_$t.

Options
—C

Generate a template, including a UUID attribute, for an interface

—C

Generate a C source-code representation of a UUID.

—version

Display the version of the Network Computing Kernel (NCK) that
this uuid_gen belongs to but do not generate a UUID. (NCK is

definition in the C syntax of NIDL.

part of the Network Computing System (NCS) on which DECrpc is
based.)

Examples
Generate a character-string representation of a UUID:
$ /etc/ncs/uuid_gen
34dc23469000.0d4.00.00.7¢.5£.00.00.00

Generate a template for an interface definition in the C syntax of NIDL:
$ /etc/ncs/uuid_gen —
%c

[

uuid (34dc239ec000.0d4.00.00.7¢c.5£.00.00.00),
version
(1)

]
interface

INTERFACENAME

(

}

Generate a template for an interface definition in the C syntax of NIDL. Redirect the
output to the file myfile.idl.
$ /etc/ncs/uuid_gen —c >myfile.idl

Generate a C source-code representation of a UUID:
$ /etc/ncs/unid_gen —C
=

{

0x34dc23af,

0x£000,

0x0000,
0x0d,

{0x00,

1-=730 Commands

0x00,

Ox7c,

Ox5f,

0x00,

0xO00}

};

uuid_gen(1ncs)

See Also

passwd(1yp), passwd(Syp), ypfiles(5yp), yppasswdd(8yp)
Guide to the Yellow Pages Service

1-784 Commands

ypwhich (1yp)
Name
ypwhich — determine which host is the current YP server or map master.

Syntax
ypwhich [-d domain] [-V1] [-V2] [ hostname]
ypwhich [-d domain] [-m mname ][-t]]
ypwhich —x

Description
The ypwhich command identifies the YP server that currently supplies yellow
pages services to a YP client. It also identifies which YP server is the master for a
map. If invoked without arguments, ypwhich returns the host name of the YP

server for the local machine. If hostname is specified, ypwhich checks that
machine to find out which YP master it is using.

Refer to yp£files(Syp) and ypserv(8yp) for an overview of the yellow pages.

Options
-V1
Identifies which server is serving v.1 YP protocol-speaking client processes.
-V2
Identifies which server is serving v.2 YP protocol-speaking client processes.
If neither version is specified, ypwhich attempts to locate the server that

supplies the current v.2 services. If there is no v.2 server currently bound,

ypwhich attempts to locate the server supplying the v.1 services. Since YP
servers and YP clients are both backward compatible, the user need seldom be

concerned about which version is currently in use.

—d

Uses domain instead of the current domain.

~m mname

Finds the master YP server for a map. No hostname can be specified with —m.
The mname argument can be a mapname, or a nickname for a map.
-t

Inhibits nickname translation and is useful if there is a mapname identical to a
nickname.

—x

Displays the map nickname table. This option lists the nicknames (mnames)
that the command knows of, and indicates the mapname associated with each
nickname.

See Also
ypfiles(Syp), rpcinfo(8nfs), ypserv(8yp), ypsetup(8yp)

Commands 1-785

Index

Special Characters
? command (TELNET), 1-690
? command (tftp), 1-698

Numbers
2780e emulator spooler, 1-2

See also 3780e emulator spooler
3780e emulator spooler, 1-3
See also 2780e emulator spooler

admin command (sccs) (cont.)