13
13
<b>master</b> [<b>-Ddtvw</b>] [<b>-c</b> <i>config</i><b>_</b><i>dir</i>] [<b>-e</b> <i>exit</i><b>_</b><i>time</i>]
16
The <a href="master.8.html"><b>master</b>(8)</a> daemon is the resident process that runs
17
Postfix daemons on demand: daemons to send or receive mes-
18
sages via the network, daemons to deliver mail locally,
19
etc. These daemons are created on demand up to a config-
20
urable maximum number per service.
22
Postfix daemons terminate voluntarily, either after being
23
idle for a configurable amount of time, or after having
24
serviced a configurable number of requests. Exceptions to
25
this rule are the resident queue manager, address verifi-
26
cation server, and the TLS session cache and pseudo-random
29
The behavior of the <a href="master.8.html"><b>master</b>(8)</a> daemon is controlled by the
30
<a href="master.5.html"><b>master.cf</b></a> configuration file, as described in <a href="master.5.html"><b>master</b>(5)</a>.
16
The <a href="master.8.html"><b>master</b>(8)</a> daemon is the resident process that runs Postfix daemons
17
on demand: daemons to send or receive messages via the network, daemons
18
to deliver mail locally, etc. These daemons are created on demand up
19
to a configurable maximum number per service.
21
Postfix daemons terminate voluntarily, either after being idle for a
22
configurable amount of time, or after having serviced a configurable
23
number of requests. Exceptions to this rule are the resident queue man-
24
ager, address verification server, and the TLS session cache and
25
pseudo-random number server.
27
The behavior of the <a href="master.8.html"><b>master</b>(8)</a> daemon is controlled by the <a href="master.5.html"><b>master.cf</b></a>
28
configuration file, as described in <a href="master.5.html"><b>master</b>(5)</a>.
34
32
<b>-c</b> <i>config</i><b>_</b><i>dir</i>
35
Read the <a href="postconf.5.html"><b>main.cf</b></a> and <a href="master.5.html"><b>master.cf</b></a> configuration files
36
in the named directory instead of the default con-
37
figuration directory. This also overrides the con-
38
figuration files for other Postfix daemon pro-
41
<b>-D</b> After initialization, run a debugger on the master
42
process. The debugging command is specified with
43
the <b><a href="postconf.5.html#debugger_command">debugger_command</a></b> in the <a href="postconf.5.html"><b>main.cf</b></a> global configu-
46
<b>-d</b> Do not redirect stdin, stdout or stderr to
47
/dev/null, and do not discard the controlling ter-
48
minal. This must be used for debugging only.
33
Read the <a href="postconf.5.html"><b>main.cf</b></a> and <a href="master.5.html"><b>master.cf</b></a> configuration files in the named
34
directory instead of the default configuration directory. This
35
also overrides the configuration files for other Postfix daemon
38
<b>-D</b> After initialization, run a debugger on the master process. The
39
debugging command is specified with the <b><a href="postconf.5.html#debugger_command">debugger_command</a></b> in the
40
<a href="postconf.5.html"><b>main.cf</b></a> global configuration file.
42
<b>-d</b> Do not redirect stdin, stdout or stderr to /dev/null, and do not
43
discard the controlling terminal. This must be used for debug-
50
46
<b>-e</b> <i>exit</i><b>_</b><i>time</i>
51
Terminate the master process after <i>exit</i><b>_</b><i>time</i> sec-
52
onds. Child processes terminate at their conve-
55
<b>-t</b> Test mode. Return a zero exit status when the <b>mas-</b>
56
<b>ter.pid</b> lock file does not exist or when that file
57
is not locked. This is evidence that the <a href="master.8.html"><b>master</b>(8)</a>
58
daemon is not running.
60
<b>-v</b> Enable verbose logging for debugging purposes. This
61
option is passed on to child processes. Multiple <b>-v</b>
62
options make the software increasingly verbose.
64
<b>-w</b> Wait in a dummy foreground process, while the real
65
master daemon initializes in a background process.
66
The dummy foreground process returns a zero exit
67
status only if the master daemon initialization is
68
successful, and if it completes in a reasonable
71
This feature is available in Postfix 2.10 and
47
Terminate the master process after <i>exit</i><b>_</b><i>time</i> seconds. Child pro-
48
cesses terminate at their convenience.
50
<b>-t</b> Test mode. Return a zero exit status when the <b>master.pid</b> lock
51
file does not exist or when that file is not locked. This is
52
evidence that the <a href="master.8.html"><b>master</b>(8)</a> daemon is not running.
54
<b>-v</b> Enable verbose logging for debugging purposes. This option is
55
passed on to child processes. Multiple <b>-v</b> options make the soft-
56
ware increasingly verbose.
58
<b>-w</b> Wait in a dummy foreground process, while the real master daemon
59
initializes in a background process. The dummy foreground
60
process returns a zero exit status only if the master daemon
61
initialization is successful, and if it completes in a reason-
64
This feature is available in Postfix 2.10 and later.
76
<b>SIGHUP</b> Upon receipt of a <b>HUP</b> signal (e.g., after "<b>postfix</b>
77
<b>reload</b>"), the master process re-reads its configu-
78
ration files. If a service has been removed from
79
the <a href="master.5.html"><b>master.cf</b></a> file, its running processes are ter-
80
minated immediately. Otherwise, running processes
81
are allowed to terminate as soon as is convenient,
82
so that changes in configuration settings affect
83
only new service requests.
68
<b>SIGHUP</b> Upon receipt of a <b>HUP</b> signal (e.g., after "<b>postfix reload</b>"), the
69
master process re-reads its configuration files. If a service
70
has been removed from the <a href="master.5.html"><b>master.cf</b></a> file, its running processes
71
are terminated immediately. Otherwise, running processes are
72
allowed to terminate as soon as is convenient, so that changes
73
in configuration settings affect only new service requests.
86
Upon receipt of a <b>TERM</b> signal (e.g., after "<b>postfix</b>
87
<b>abort</b>"), the master process passes the signal on to
88
its child processes and terminates. This is useful
89
for an emergency shutdown. Normally one would ter-
90
minate only the master ("<b>postfix stop</b>") and allow
76
Upon receipt of a <b>TERM</b> signal (e.g., after "<b>postfix abort</b>"), the
77
master process passes the signal on to its child processes and
78
terminates. This is useful for an emergency shutdown. Normally
79
one would terminate only the master ("<b>postfix stop</b>") and allow
91
80
running processes to finish what they are doing.
94
Problems are reported to <b>syslogd</b>(8). The exit status is
95
non-zero in case of problems, including problems while
96
initializing as a master daemon process in the background.
83
Problems are reported to <b>syslogd</b>(8). The exit status is non-zero in
84
case of problems, including problems while initializing as a master
85
daemon process in the background.
100
After initialization, start a debugger as specified
101
with the <b><a href="postconf.5.html#debugger_command">debugger_command</a></b> configuration parameter
102
in the <a href="postconf.5.html"><b>main.cf</b></a> configuration file.
89
After initialization, start a debugger as specified with the
90
<b><a href="postconf.5.html#debugger_command">debugger_command</a></b> configuration parameter in the <a href="postconf.5.html"><b>main.cf</b></a> configu-
104
93
<b>MAIL_CONFIG</b>
105
94
Directory with Postfix configuration files.
107
96
<b>CONFIGURATION PARAMETERS</b>
108
Unlike most Postfix daemon processes, the <a href="master.8.html"><b>master</b>(8)</a> server
109
does not automatically pick up changes to <a href="postconf.5.html"><b>main.cf</b></a>. Changes
110
to <a href="master.5.html"><b>master.cf</b></a> are never picked up automatically. Use the
111
"<b>postfix reload</b>" command after a configuration change.
97
Unlike most Postfix daemon processes, the <a href="master.8.html"><b>master</b>(8)</a> server does not
98
automatically pick up changes to <a href="postconf.5.html"><b>main.cf</b></a>. Changes to <a href="master.5.html"><b>master.cf</b></a> are
99
never picked up automatically. Use the "<b>postfix reload</b>" command after
100
a configuration change.
113
102
<b>RESOURCE AND RATE CONTROLS</b>
114
103
<b><a href="postconf.5.html#default_process_limit">default_process_limit</a> (100)</b>
115
The default maximal number of Postfix child pro-
116
cesses that provide a given service.
104
The default maximal number of Postfix child processes that pro-
105
vide a given service.
118
107
<b><a href="postconf.5.html#max_idle">max_idle</a> (100s)</b>
119
The maximum amount of time that an idle Postfix
120
daemon process waits for an incoming connection
121
before terminating voluntarily.
108
The maximum amount of time that an idle Postfix daemon process
109
waits for an incoming connection before terminating voluntarily.
123
111
<b><a href="postconf.5.html#max_use">max_use</a> (100)</b>
124
The maximal number of incoming connections that a
125
Postfix daemon process will service before termi-
112
The maximal number of incoming connections that a Postfix daemon
113
process will service before terminating voluntarily.
128
115
<b><a href="postconf.5.html#service_throttle_time">service_throttle_time</a> (60s)</b>
129
How long the Postfix <a href="master.8.html"><b>master</b>(8)</a> waits before forking
130
a server that appears to be malfunctioning.
116
How long the Postfix <a href="master.8.html"><b>master</b>(8)</a> waits before forking a server
117
that appears to be malfunctioning.
132
119
Available in Postfix version 2.6 and later:
134
121
<b><a href="postconf.5.html#master_service_disable">master_service_disable</a> (empty)</b>
135
Selectively disable <a href="master.8.html"><b>master</b>(8)</a> listener ports by
136
service type or by service name and type.
122
Selectively disable <a href="master.8.html"><b>master</b>(8)</a> listener ports by service type or
123
by service name and type.
138
125
<b>MISCELLANEOUS CONTROLS</b>
139
126
<b><a href="postconf.5.html#config_directory">config_directory</a> (see 'postconf -d' output)</b>
140
The default location of the Postfix <a href="postconf.5.html">main.cf</a> and
141
<a href="master.5.html">master.cf</a> configuration files.
127
The default location of the Postfix <a href="postconf.5.html">main.cf</a> and <a href="master.5.html">master.cf</a> con-
143
130
<b><a href="postconf.5.html#daemon_directory">daemon_directory</a> (see 'postconf -d' output)</b>
144
The directory with Postfix support programs and
131
The directory with Postfix support programs and daemon programs.
147
133
<b><a href="postconf.5.html#debugger_command">debugger_command</a> (empty)</b>
148
The external command to execute when a Postfix dae-
149
mon program is invoked with the -D option.
134
The external command to execute when a Postfix daemon program is
135
invoked with the -D option.
151
137
<b><a href="postconf.5.html#inet_interfaces">inet_interfaces</a> (all)</b>
152
The network interface addresses that this mail sys-
153
tem receives mail on.
138
The network interface addresses that this mail system receives
155
141
<b><a href="postconf.5.html#inet_protocols">inet_protocols</a> (all)</b>
156
The Internet protocols Postfix will attempt to use
157
when making or accepting connections.
142
The Internet protocols Postfix will attempt to use when making
143
or accepting connections.
159
145
<b><a href="postconf.5.html#import_environment">import_environment</a> (see 'postconf -d' output)</b>
160
The list of environment parameters that a Postfix
161
process will import from a non-Postfix parent
146
The list of environment parameters that a Postfix process will
147
import from a non-Postfix parent process.
164
149
<b><a href="postconf.5.html#mail_owner">mail_owner</a> (postfix)</b>
165
The UNIX system account that owns the Postfix queue
166
and most Postfix daemon processes.
150
The UNIX system account that owns the Postfix queue and most
151
Postfix daemon processes.
168
153
<b><a href="postconf.5.html#process_id">process_id</a> (read-only)</b>
169
The process ID of a Postfix command or daemon
154
The process ID of a Postfix command or daemon process.
172
156
<b><a href="postconf.5.html#process_name">process_name</a> (read-only)</b>
173
The process name of a Postfix command or daemon
157
The process name of a Postfix command or daemon process.
176
159
<b><a href="postconf.5.html#queue_directory">queue_directory</a> (see 'postconf -d' output)</b>
177
The location of the Postfix top-level queue direc-
160
The location of the Postfix top-level queue directory.
180
162
<b><a href="postconf.5.html#syslog_facility">syslog_facility</a> (mail)</b>
181
163
The syslog facility of Postfix logging.
183
165
<b><a href="postconf.5.html#syslog_name">syslog_name</a> (see 'postconf -d' output)</b>
184
The mail system name that is prepended to the
185
process name in syslog records, so that "smtpd"
186
becomes, for example, "postfix/smtpd".
166
The mail system name that is prepended to the process name in
167
syslog records, so that "smtpd" becomes, for example, "post-
189
To expand the directory names below into their actual val-
190
ues, use the command "<b>postconf <a href="postconf.5.html#config_directory">config_directory</a></b>" etc.
171
To expand the directory names below into their actual values, use the
172
command "<b>postconf <a href="postconf.5.html#config_directory">config_directory</a></b>" etc.
192
174
$<a href="postconf.5.html#config_directory">config_directory</a>/<a href="postconf.5.html">main.cf</a>, global configuration file.
193
175
$<a href="postconf.5.html#config_directory">config_directory</a>/<a href="master.5.html">master.cf</a>, master server configuration file.
added
removed
html/master.8.html
