|
|
1.1 root 1: .TH ENVIRON 5
2: .CT 2 proc_man
3: .SH NAME
4: environ \- user environment
5: .SH SYNOPSIS
6: .B extern char **environ;
7: .SH DESCRIPTION
8: An array of strings called the `environment' is
9: made available by
10: .IR exec (2)
11: when a process begins.
12: By convention these strings have either the form
13: .IB name = value ,
14: defining a variable, or
15: .IB name (){ value } ,
16: defining a function; see
17: .IR sh (1).
18: The following variables are used by various commands:
19: .TF TERMCAP
20: .TP
21: .B PATH
22: The sequence of directory prefixes that
23: .I sh,
24: .IR time (1),
25: .IR nice (1),
26: etc.,
27: apply in searching for a file known by an incomplete path name.
28: The prefixes are separated by
29: .LR : .
30: .IR Login (8)
31: sets
32: .LR PATH=:/bin:/usr/bin .
33: .PD
34: .TP
35: .B HOME
36: A user's login directory, set by
37: .IR login (8)
38: from the password file
39: .IR passwd (5).
40: .TP
41: .B TERM
42: The kind of terminal for which output is to be prepared.
43: This information is used by commands, such as
44: .I nroff
45: or
46: .IR plot (1),
47: which may exploit special terminal capabilities.
48: See
49: .FR /etc/termcap ,
50: described in
51: .IR termcap (5),
52: for a list of terminal types.
53: .TP
54: .B SHELL
55: The name of the login shell.
56: .PP
57: The environment may be queried by
58: .IR getenv (3)
59: or by the
60: .L set
61: or
62: .L whatis
63: commands of
64: .IR sh (1).
65: Names may be placed in the environment by the
66: .L export
67: command and by
68: .IB name = value
69: arguments of
70: .IR sh (1).
71: Names may also be placed in the environment at the point of an
72: .IR exec (2).
73: It is unwise to conflict with
74: certain
75: .IR sh (1)
76: variables that are frequently exported by
77: .F .profile
78: files:
79: .BR MAIL ,
80: .BR PS1 ,
81: .BR PS2 ,
82: .BR IFS .
83: .SH SEE ALSO
84: .IR sh (1),
85: .IR printenv (1),
86: .IR exec (2),
87: .IR getenv (3),
88: .IR term (6)
89: .SH BUGS
90: Function definitions in the environment break some old programs,
91: including old shells.
This archive runs on limited infrastructure. Preserving old code on modern bandwidth. Automated agents are requested to crawl responsibly.