$manlookup

env

(1)

run a program in a modified environment

env [OPTION]... [-] [NAME=VALUE]... [COMMAND [ARG]...]

Options

13
-a--argv0ARG

pass ARG as the zeroth argument of COMMAND

-i--ignore-environment

start with an empty environment

-0--null

end each output line with NUL, not newline

-u--unsetNAME

remove variable from the environment

-C--chdirDIR

change working directory to DIR

-S--split-stringS

process and split S into separate arguments; used to pass multiple arguments on shebang lines

--block-signalSIG

block delivery of SIG signal(s) to COMMAND

--default-signalSIG

reset handling of SIG signal(s) to the default

--ignore-signalSIG

set handling of SIG signal(s) to do nothing

--list-signal-handling

list non default signal handling to stderr

-v--debug

print verbose information for each processing step

--help

display this help and exit

--version

output version information and exit

DESCRIPTION

Set each NAME to VALUE in the environment and run COMMAND.

Mandatory arguments to long options are mandatory for short options too.

pass ARG as the zeroth argument of COMMAND
start with an empty environment
-0, --null
end each output line with NUL, not newline
remove variable from the environment
change working directory to DIR
process and split S into separate arguments; used to pass multiple arguments on shebang lines
block delivery of SIG signal(s) to COMMAND
reset handling of SIG signal(s) to the default
set handling of SIG signal(s) to do nothing
list non default signal handling to stderr
print verbose information for each processing step
display this help and exit
output version information and exit

A mere - implies -i. If no COMMAND, print the resulting environment.

SIG may be a signal name like 'PIPE', or a signal number like '13'. Without SIG, all known signals are included. Multiple signals can be comma-separated. An empty SIG argument is a no-op.

125
if the env command itself fails
126
if COMMAND is found but cannot be invoked
127
if COMMAND cannot be found
-
the exit status of COMMAND otherwise

NOTES

POSIX's exec(3p) pages says:

"many existing applications wrongly assume that they start with certain signals set to the default action and/or unblocked.... Therefore, it is best not to block or ignore signals across execs without explicit reason to do so, and especially not to block signals across execs of arbitrary (not closely cooperating) programs."

AUTHOR

Written by Richard Mlynarik, David MacKenzie, and Assaf Gordon.

REPORTING BUGS

GNU coreutils online help: https://www.gnu.org/software/coreutils/
Report any translation bugs to https://translationproject.org/team/

See also