env - set the environment for command invocation
env [-i][name=value]... [utility [argument...]] env [-][name=value]... [utility [argument...]]
The env utility will obtain the current environment, modify it according to its arguments, then invoke the utility named by the utility operand with the modified environment.
Optional arguments will be passed to utility.
If no utility operand is specified, the resulting environment will be written to the standard output, with one name=value pair per line.
The env utility supports the XBD specification, Utility Syntax Guidelines , except for its non-standard usage of "-".
The following options are supported:
- Invoke utility with exactly the environment specified by the arguments; the inherited environment will be ignored completely.
The following operands are supported:
- Arguments of the form name=value modify the execution environment, and are placed into the inherited environment before the utility is invoked.
- The name of the utility to be invoked. If the utility operand names any of the special built-in utilities in
Special Built-in Utilities, the results are undefined.
- A string to pass as an argument for the invoked utility.
The following environment variables affect the execution of env:
- Provide a default value for the internationalisation variables that are unset or null. If LANG is unset or null, the corresponding value from the implementation-dependent default locale will be used. If any of the internationalisation variables contains an invalid setting, the utility will behave as if none of the variables had been defined.
- If set to a non-empty string value, override the values of all the other internationalisation variables.
- Determine the locale for the interpretation of sequences of bytes of text data as characters (for example, single- as opposed to multi-byte characters in arguments).
- Determine the locale that should be used to affect the format and contents of diagnostic messages written to standard error.
- Determine the location of message catalogues for the processing of LC_MESSAGES .
- Determine the location of the utility, as described in the XBD specification, Environment Variables . If PATH is specified as a name=value operand to env, the value given will be used in the search for utility.
If no utility operand is specified, each name=value pair in the resulting environment will be written in the form:
"%s=%s\n", <name>, <value>
If the utility operand is specified, the env utility will not write to standard output.
Used only for diagnostic messages.
If the utility utility is invoked, the exit status of env will be the exit status of utility; otherwise, the env utility will exit with one of the following values:
- The env utility completed successfully.
- An error occurred in the env utility.
- The utility specified by utility was found but could not be invoked.
- The utility specified by utility could not be found.
The command, env, nice, nohup, time and xargs utilities have been specified to use exit code 127 if an error occurs so that applications can distinguish "failure to find a utility" from "invoked utility exited with an error indication". The value 127 was chosen because it is not commonly used for other meanings; most utilities use small values for "normal error conditions" and the values above 128 can be confused with termination due to receipt of a signal. The value 126 was chosen in a similar manner to indicate that the utility could be found, but not invoked. Some scripts produce meaningful error messages differentiating the 126 and 127 cases. The distinction between exit codes 126 and 127 is based on KornShell practice that uses 127 when all attempts to exec the utility fail with [ENOENT], and uses 126 when any attempt to exec the utility fails for any other reason.
Historical implementations of the env utility use the XSH specification execvp() or execlp() functions to invoke the specified utility; this provides better performance and keeps users from having to escape characters with special meaning to the shell. Therefore, shell functions, special built-ins and built-ins that are only provided by the shell are not found.
The following command:invokes the command mygrep with a new PATH value as the only entry in its environment. In this case, PATH is used to locate mygrep, which then must reside in /mybin.
env -i PATH=/mybin mygrep xyz myfile
Parameters and Variables.