ENV(1) >>>>>>>>>> >>>>>>> ENV(1)
>>>>>
env - run a program in a modified environment
>>>>
env [>>>>>>]... [-]
[>>>>>=>>>>>>>>]... [>>>>>>>
[>>>]...]
>>>>
>>>>>>>> >>>>> >>>>> >>
>>>>>>>> > >>>>>>>> >
>>>>>>> >>>>>>>.
>>>>>>>> >>>>>>>>> >>
>>>> >>>>>> >> >>>>>>>> >
>> >>>>>> >>>>>> >>>>>>.
-a, --argv0=>>>
pass ARG as the zeroth argument of COMMAND
-i, --ignore-environment
>>>>>> >>>>>>>
>>>>>>>>>
-0, --null
>>>>>>>> >>>>> >>>>>>>
>>> >> >>>>>, >> >>>>>
>>>>>
-u, --unset=>>>>>
>>>>>> >>>>>>>>>> >>
>>>>>>>>
-C, --chdir=>>>
>>>> >>>>>
>>>>>>>>>>>> > >>>
-S, --split-string=S
>>>>>>>> > >>>> ,,S" >>
>>>>>>>> >>>>>>>>>;
>>>>>>> >> >>
>>>>>>>>>>>> >>>>
>>>>>>>>>> >> ,,shebang"
>>>>>>
--block-signal[=>>>]
>>>>>>>> >>>>> >>>
>>>>>>> >>>>>>>
--default-signal[=>>>]
>>>>> >>>>>>>> >>>
>>>>>>>> >>
>>>>>>>>>>>>>
--ignore-signal[=>>>]
>>>>>>>> >>>>>>>> >>>
>>>>>>>> >> >> >>>>
>>>>>
--list-signal-handling
>>>>>>>>
>>>>>>>>>>>>>>>
>>>>>>>> >>>>>>>> >>
>>>>>>>>>> >>>>>>
-v, --debug
>>>>>>>> >>>>>>>
>>>>>>> >> >>>>> >>>>>
>>>>>>
--help >>>>>>>>> >>> >>>>> >
>>>>>>
--version
>>>>>>>> >>>>>>> >
>>>>>> > >>>>>>
>>>> - >>>>>>>>>>> -i. >>>
>>>> >>>>>>>, >>>>>>>>
>>>>>>>>>>>>> >>>>>>>>.
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 >>> >>>> >>>>>>> env >>
>>>>
126 >>> >> >>>>>>> >>>>>>
>>> >> >> >>>> >>>>>>>>
127 >>> >> >>>>>>> >> >>>>
>>>>
- > >>>>>>>>> >>>>>>>
>>>>> >>>>>>>
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': >>>> >>>>> >>>>>>>> >>> >>>>>>>>>>>>>
See the full documentation for more details.
>>>>>>>>
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."
>>>>>
>>>>>>>> >>>>>> >>>>>>>>,
>>>>>> >>> >>>>> > >>>>
>>>>>>.
>>>>>>>>>>>> >>>>>>>
>>>>>> >>>>>>>>> >>:
bug-coreutils@gnu.org
>>> coreutils >>>>>>> >>>>>>>>:
>>>>> >>>>> >> >>>>>>>>>
>>> >>>>>>>>:
>>>>>> > >>>>>>>
>>>>>>>>> >>
>>>>>>>> >>>>>
Copyright (C) 2026 Free Software Foundation, Inc. >>>>>>>
>>>>3+: >>> >>> >>>>>> 3 >>>
>>>>>>> .
>>> >> >>>>>>>> >>>>>>>:
>>>>>>>> >>> >> >> >>>>>> >
>>>>>>>>>>>>>. >> >>>>>>>
>>>>>>> >>>>>>>>>, >
>>>>>>>> >>>>>>>>>>
>>>>>>>.
>>>>>> >>>>>>
sigaction(2), sigprocmask(2), signal(7)
>>> >>>>>>>>>>>>> >>
>>>>>> >>
>>> >> >>>>>>>> >>
>>>>>>>> >>>>> >>>>>>> ,,info
'(coreutils) env invocation'"
>>>>>>
>>>>>> >>>>>> >>>
>>>>>>>> >> >>>>>>>>>>>
>>> >>>>>>>>>
>>>> >>>>>> >> >>>>>>>>>
>>>>>>>>>>>>>; >> >>>>>>
>>>>>>>>> >>>>>
>>>>>>>>>> >>> >>>>>
>>>>> >>>>>>> >>>>>>> 3
>>>
>>>>>>. >> >>>>>>>>>>
>>>>>>> >>>>>>>>>>>.
>>> >>>>>>>>> >>>>>> >
>>>>>>> >>> >>>>>>>>
>>>>>>>>>>, >>>>>>>>
>->>>>>> TODO <>.
>>> coreutils 9.11 >>>>>> 2026 ENV(1)