1 .\" Copyright (c) 1993 Michael Haardt (michael@moria.de),
2 .\" Fri Apr 2 11:32:09 MET DST 1993
3 .\" and Andries Brouwer (aeb@cwi.nl), Fri Feb 14 21:47:50 1997.
5 .\" This is free documentation; you can redistribute it and/or
6 .\" modify it under the terms of the GNU General Public License as
7 .\" published by the Free Software Foundation; either version 2 of
8 .\" the License, or (at your option) any later version.
10 .\" The GNU General Public License's references to "object code"
11 .\" and "executables" are to be interpreted as the output of any
12 .\" document formatting or typesetting system, including
13 .\" intermediate and printed output.
15 .\" This manual is distributed in the hope that it will be useful,
16 .\" but WITHOUT ANY WARRANTY; without even the implied warranty of
17 .\" MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
18 .\" GNU General Public License for more details.
20 .\" You should have received a copy of the GNU General Public
21 .\" License along with this manual; if not, write to the Free
22 .\" Software Foundation, Inc., 59 Temple Place, Suite 330, Boston, MA 02111,
25 .\" Modified Sun Jul 25 10:45:30 1993 by Rik Faith (faith@cs.unc.edu)
26 .\" Modified Sun Jul 21 21:25:26 1996 by Andries Brouwer (aeb@cwi.nl)
27 .\" Modified Mon Oct 21 17:47:19 1996 by Eric S. Raymond (esr@thyrsus.com)
28 .\" Modified Wed Aug 27 20:28:58 1997 by Nicolás Lichtmaier (nick@debian.org)
29 .\" Modified Mon Sep 21 00:00:26 1998 by Andries Brouwer (aeb@cwi.nl)
30 .\" Modified Wed Jan 24 06:37:24 2001 by Eric S. Raymond (esr@thyrsus.com)
31 .\" Modified Thu Dec 13 23:53:27 2001 by Martin Schulze <joey@infodrom.org>
33 .TH ENVIRON 7 2001-12-14 "Linux" "Linux Programmer's Manual"
35 environ \- user environment
38 .BI "extern char **" environ ;
44 points to an array of strings called the "environment".
45 (This variable must be declared in the user program,
46 but is declared in the header file
48 in case the header files came from libc4 or libc5, and
49 in case they came from glibc and
52 This array of strings is made available to the process by the
54 call that started the process.
55 By convention these strings
56 have the form "\fIname\fP\fB=\fP\fIvalue\fP".
60 The name of the logged-in user (used by some BSD-derived programs).
63 The name of the logged-in user (used by some System-V derived programs).
66 A user's login directory, set by
68 from the password file
72 The name of a locale to use for locale categories when not overridden
73 by \fBLC_ALL\fP or more specific environment variables like
74 \fBLC_COLLATE\fP, \fBLC_CTYPE\fP, \fBLC_MESSAGES\fP, \fBLC_MONETARY\fP,
75 \fBLC_NUMERIC\fP, \fBLC_TIME\fP, cf.
79 The sequence of directory prefixes that
82 programs apply in searching for a file known by an incomplete pathname.
83 The prefixes are separated by '\fB:\fP'.
84 (Similarly one has \fBCDPATH\fP used by some shells to find the target
85 of a change directory command, \fBMANPATH\fP used by
88 find manual pages, etc.)
91 The current working directory.
95 The pathname of the user's login shell.
98 The terminal type for which output is to be prepared.
101 The user's preferred utility to display text files.
104 The user's preferred utility to edit text files.
107 .\" The user's preferred utility to browse URLs. Sequence of colon-separated
108 .\" browser commands. See http://www.catb.org/~esr/BROWSER/ .
110 Further names may be placed in the environment by the \fIexport\fP
111 command and "name=value" in
113 or by the \fIsetenv\fP command if you use
115 Arguments may also be placed in the
116 environment at the point of an
118 A C program can manipulate its environment using the functions
125 Note that the behavior of many programs and library routines is
126 influenced by the presence or value of certain environment variables.
130 .BR LANG ", " LANGUAGE ", " NLSPATH ", " LOCPATH ", "
131 .BR LC_ALL ", " LC_MESSAGES ", "
132 etc. influence locale handling, cf.
136 influences the path prefix of names created by
138 and other routines, the temporary directory used by
140 and other programs, etc.
142 .BR LD_LIBRARY_PATH ", " LD_PRELOAD
143 and other LD_* variables influence
144 the behavior of the dynamic loader/linker.
147 makes certain programs and library routines follow
148 the prescriptions of POSIX.
158 gives the name of a file containing aliases
160 .BR gethostbyname (3).
163 give time zone information used by
165 and through that by functions like
174 gives information on how to address a given terminal
175 (or gives the name of a file containing such information).
177 .BR COLUMNS " and " LINES
178 tell applications about the window size, possibly overriding the actual size.
180 .BR PRINTER " or " LPDEST
181 may specify the desired printer to use.
187 Clearly there is a security risk here.
188 Many a system command has been
189 tricked into mischief by a user who specified unusual values for
190 .BR IFS " or " LD_LIBRARY_PATH .
192 There is also the risk of name space pollution.
197 allow overriding of default utility names from the
198 environment with similarly named variables in all caps.
201 to select the desired C compiler (and similarly
211 However, in some traditional uses such an environment variable
212 gives options for the program instead of a pathname.
218 Such usage is considered mistaken, and to be avoided in new
222 should consider renaming their option to