1 .\" Copyright (c) 1983 Regents of the University of California.
2 .\" All rights reserved. The Berkeley software License Agreement
3 .\" specifies the terms and conditions for redistribution.
5 .\" @(#)environ.7 6.1 (Berkeley) 5/20/85
7 .TH ENVIRON 7 "May 20, 1985"
10 environ \- user environment
12 .B "extern char *const *environ;"
14 An array of strings called the `environment' is made available by
16 when a process begins. By convention these strings have the form
18 The following names are used by various commands:
21 The sequence of directory prefixes that
25 etc., apply in searching for a file known by an incomplete path name.
26 The prefixes are separated by `:'.
28 .BR PATH=:/bin:/usr/bin .
29 Note that the empty space between the `=' and the `:' indicates the current
30 directory. Security aware people move the extra `:' to the end of their
34 A user's login directory, set by
36 from the password file
40 The kind of terminal for which output is to be prepared.
41 This information is used by programs that wish to exploit special
42 terminal capabilities, a screen oriented text editor for instance.
43 The terminal type is set by
49 The file name of the users login shell, set by
51 from the password file
55 The string describing the terminal in TERM, or the name of the termcap file,
61 A startup list of commands read by
65 The login name of the user, set by
67 from the password file
71 Set to the same value as
73 BSD derived systems have
77 so modern systems have both to avoid problems.
80 Further names may be placed in the environment by the
86 Arguments may also be placed in their environment by
89 Or in the environment of another program by building a new environment
90 for one of the exec functions that accepts an environment list, like
94 It is unwise to conflict with certain
96 variables that are frequently set and/or exported by `.profile' files: