env(3) [plan9 man page]

ENV(3)							     Library Functions Manual							    ENV(3)

NAME

       env - environment variables

SYNOPSIS

       bind #e /env

       /env/var1
       /env/var2
	...

DESCRIPTION

       The env device serves a one-level directory containing files with arbitrary names and contents.	The intention is that the file name is the
       name of an environment variable (see rc(1)), and the content is the variable's current value.

       When a fork(2) system call creates a new process, both the parent and the child continue to see exactly the same files in the  env  device:
       changes made in either process can be noticed by the other.  In contrast, an rfork system call with the RFENVG bit set (see fork(2)) causes
       a split: initially both process groups see the same environment files, but any changes made in one process group cannot be noticed  by  the
       other.  An rfork with RFCENVG splits and then clears the environment.

SEE ALSO

       rc(1), fork(2)

SOURCE

       /sys/src/9/port/devenv.c

BUGS

       A write starting at an offset after the current extent of a file yields an error instead of zero filling.

																	    ENV(3)

ENV(1)							    BSD General Commands Manual 						    ENV(1)

NAME

     env -- set and print environment

SYNOPSIS

     env [-i] [name=value ...] [utility [argument ...]]

DESCRIPTION

     env executes utility after modifying the environment as specified on the command line.  The option name=value specifies an environmental
     variable, name, with a value of value.  The option '-i' causes env to completely ignore the environment it inherits.

     If no utility is specified, env prints out the names and values of the variables in the environment, with one name=value pair per line.

DIAGNOSTICS

     If the utility is invoked, the exit status of env shall be the exit status of utility; otherwise, the env utility exits with one of the fol-
     lowing values:

     0	     The env utility completed successfully

     1-125   An error occurred in the env utility.

     126     The utility specified by utility was found, but could not be invoked.

     127     The utility specified by utility could not be found.

COMPATIBILITY

     The historic - option has been deprecated but is still supported in this implementation.

SEE ALSO

     execvp(3), environ(7)

STANDARDS

     The env utility conforms to IEEE Std 1003.2-1992 (``POSIX.2'').

BUGS

     env doesn't handle commands with equal (``='') signs in their names, for obvious reasons.

BSD
								  August 27, 1993							       BSD