Indicate that env(1) allows you to supply arguments to the utility it

executes in the usage() message and manual page. Use "utility" instead of
"command" in both places to emphasise that shell builtins etc. will not work,
and to be consistent with the terminology used by POSIX.

PR:		39210
Submitted by:	Danny J. Zerkel <dzerkel@columbus.rr.com>
MFC after:	1 week
This commit is contained in:
tjr 2002-06-19 07:09:44 +00:00
parent bfa1cb192c
commit e03fb12529
2 changed files with 8 additions and 8 deletions

2
usr.bin/env/env.c vendored
View File

@ -92,6 +92,6 @@ static void
usage()
{
(void)fprintf(stderr,
"usage: env [-] [-i] [name=value ...] [command]\n");
"usage: env [-] [-i] [name=value ...] [utility [argument ...]]\n");
exit(1);
}

View File

@ -47,7 +47,7 @@
.Op Fl
.Op Fl i
.Op Ar name Ns = Ns Ar value ...
.Op Ar command
.Op Ar utility Oo Ar argument ... Oc
.Sh DESCRIPTION
The
.Nm
@ -68,7 +68,7 @@ manual page.
The
.Nm env
utility executes
.Ar command
.Ar utility
after modifying the environment as
specified on the command line.
The option
@ -83,7 +83,7 @@ The options are as follows:
.Bl -tag -width indent
.It Fl i
Execute the
.Ar command
.Ar utility
with only those environment values specified.
The environment inherited
by
@ -95,7 +95,7 @@ Identical to the
option, available for backward compatibility.
.El
.Pp
If no command is specified,
If no utility is specified,
.Nm env
prints out the names and values
of the variables in the environment, with one name/value pair per line.
@ -124,10 +124,10 @@ as well as set up the environment as desired.
.Pp
.Ex -std env
An exit status of 126 indicates
.Ar command
.Ar utility
was found, but could not be executed.
An exit status of 127 indicates
.Ar command
.Ar utility
could not be found.
.Sh SEE ALSO
.Xr csh 1 ,
@ -147,5 +147,5 @@ command appeared in
.Sh BUGS
The
.Nm env
utility doesn't handle commands with equal (``='') signs in their
utility doesn't handle utility arguments with equal (``='') signs in their
names, for obvious reasons.