1 .\" $NetBSD: environ.7,v 1.4 1995/07/03 19:45:07 jtc Exp $
3 .\" Copyright (c) 1983, 1990, 1993
4 .\" The Regents of the University of California. All rights reserved.
6 .\" Redistribution and use in source and binary forms, with or without
7 .\" modification, are permitted provided that the following conditions
9 .\" 1. Redistributions of source code must retain the above copyright
10 .\" notice, this list of conditions and the following disclaimer.
11 .\" 2. Redistributions in binary form must reproduce the above copyright
12 .\" notice, this list of conditions and the following disclaimer in the
13 .\" documentation and/or other materials provided with the distribution.
14 .\" 3. All advertising materials mentioning features or use of this software
15 .\" must display the following acknowledgement:
16 .\" This product includes software developed by the University of
17 .\" California, Berkeley and its contributors.
18 .\" 4. Neither the name of the University nor the names of its contributors
19 .\" may be used to endorse or promote products derived from this software
20 .\" without specific prior written permission.
22 .\" THIS SOFTWARE IS PROVIDED BY THE REGENTS AND CONTRIBUTORS ``AS IS'' AND
23 .\" ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE
24 .\" IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE
25 .\" ARE DISCLAIMED. IN NO EVENT SHALL THE REGENTS OR CONTRIBUTORS BE LIABLE
26 .\" FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL
27 .\" DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS
28 .\" OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
29 .\" HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT
30 .\" LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY
31 .\" OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF
34 .\" @(#)environ.7 8.3 (Berkeley) 4/19/94
43 .Ar extern char **environ ;
45 An array of strings called the
49 when a process begins. By convention these strings have the form
51 The following names are used by various commands:
52 .Bl -tag -width BLOCKSIZE
54 The size of the block units used by several commands, most notably
59 BLOCKSIZE may be specified in units of a byte by specifying a number,
60 in units of a kilobyte by specifying a number followed by ``K'' or
61 ``k'', in units of a megabyte by specifying a number followed by ``M''
62 or ``m'' and in units of a gigabyte by specifying a number followed
64 Sizes less than 512 bytes or greater than a gigabyte are ignored.
66 A startup list of commands read by
71 A user's login directory, set by
73 from the password file
76 The sequence of directories, separated by colons, searched by
81 etc, when looking for an executable file.
82 PATH is set to ``/usr/bin:/bin'' initially by
85 The name of the default printer to be used by
91 The full pathname of the user's login shell.
93 The kind of terminal for which output is to be prepared.
94 This information is used by commands, such as
96 which may exploit special terminal capabilities. See
101 The directory in which to store temporary files.
102 Most applications use either
106 Setting this variable will make them use another directory.
108 The timezone to use when displaying dates.
109 The normal format is a pathname relative to
110 .Dq /usr/share/zoneinfo .
111 For example, the command
112 .Dq env TZ=US/Pacific date
113 displays the current time in California.
116 for more information.
118 The login name of the user.
120 Deprecated synonym of
122 (for backwards compatibility).
125 Further names may be placed in the environment by the
135 It is unwise to change certain
137 variables that are frequently exported by
145 unless you know what you are doing.
147 Programs can query and modify the environment, using the environment routines
153 Direct access can be made through the global variable
155 though it is recommended that changes to the enviroment still be made through
156 the environment routines.
158 Shared libraries and bundles don't have direct access to
160 which is only available to the loader
162 when a complete program is being linked.
163 The environment routines can still be used, but if direct access to
169 can be used to retrieve the address of
189 manual page appeared in