env1
Run a program in a modified environment
Usage
env [OPTION] ...
[-]
[NAME=VALUE] ...
[COMMAND
[ARG] ...]
Overview
Set each NAME to VALUE in the environment and run COMMAND.
Mandatory arguments to long options are mandatory for short options too.
-
-a, --argv0=ARG -
pass ARG as the zeroth argument of COMMAND
-
-i, --ignore-environment -
start with an empty environment
-
--env0-from=FILE -
read NUL-delimited environment entries from FILE
-
-0, --null -
end each output line with NUL, not newline
-
-u, --unset=NAME -
remove variable from the environment
-
-C, --chdir=DIR -
change working directory to DIR
-
-S, --split-string=S -
process and split S into separate arguments; used to pass multiple arguments on shebang lines
-
--block-signal[=SIG] -
block delivery of SIG signal(s) to COMMAND
-
--default-signal[=SIG] -
reset handling of SIG signal(s) to the default
-
--ignore-signal[=SIG] -
set handling of SIG signal(s) to do nothing
-
--list-signal-handling -
list non default signal handling to standard error
-
-v, --debug -
print verbose information for each processing step
-
--help -
display this help and exit
-
--version -
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.
Exit status:
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 |
Script option handling
The -S option allows specifying multiple arguments in a script. Running a script named 1.pl containing the following first line:
#!/usr/bin/env -S perl -w -T ...
Will execute perl -w -T 1.pl
Without the '-S' parameter the script will likely fail with:
/usr/bin/env: 'perl -w -T': No such file or directory
See the full documentation for more details.
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."
Releases
19 releases since Debian 1.1 (Buzz); the text changed 15 times.
--argv0 since Debian 13 (Trixie);
--block-signal since Debian 11 (Bullseye);
--chdir since Debian 10 (Buster);
--debug since Debian 10 (Buster);
--default-signal since Debian 11 (Bullseye);
--env0-from since Arch Linux 2026-11-01;
--ignore-signal since Debian 11 (Bullseye);
--list-signal-handling since Debian 11 (Bullseye);
--null since Debian 6.0 (Squeeze);
--split-string since Debian 10 (Buster);
-0 since Debian 6.0 (Squeeze);
-C since Debian 10 (Buster);
-S since Debian 10 (Buster);
-a since Debian 13 (Trixie);
-v since Debian 10 (Buster).
- until Debian 2.1 (Slink).