Lines Matching refs:instance
5 # Postfix multi-instance API
15 # activities between the postfix(1) command and a multi-instance
18 # With multi-instance support, the default Postfix instance
19 # is always required. This instance is identified by the
24 # Multi-instance support is backwards compatible: when you
25 # run only one Postfix instance, commands such as "postfix
38 # to find out what Postfix instances exist in a multi-instance
44 # a multi-instance configuration.
48 # To manage a specific Postfix instance, specify its configuration
53 # Alternatively, the postfix(1) command accepts the instance's
62 # By default, the postfix(1) command operates in single-instance
66 # Postfix instance, that upgrade the configuration of one
67 # Postfix instance, and so on.
69 # When the postfix(1) command operates in multi-instance mode
71 # stop, etc. commands for each Postfix instance. This
72 # multiplication of commands is handled by a multi-instance
75 # Turning on postfix(1) multi-instance mode goes as follows:
76 # in the default Postfix instance's main.cf file, 1) specify
77 # the pathname of a multi-instance manager program with the
98 # In multi-instance mode, the postfix(1) command invokes the
100 # file. This multi-instance manager in turn executes the
101 # postfix(1) command in single-instance mode for each Postfix
102 # instance.
104 # To illustrate the main ideas behind multi-instance operation,
105 # below is an example of a simple but useful multi-instance
140 # Each Postfix instance has its own main.cf file with parameters
141 # that control how the multi-instance manager operates on
142 # that instance. This section discusses the most important
146 # multi-instance manager to start (stop, etc.) the corresponding
147 # Postfix instance. For safety reasons, this setting is not
152 # etc. The multi-instance manager will not start such an
153 # instance, and it will skip commands such as "stop" or "flush"
154 # that require a running Postfix instance. The multi-instance
158 # instance is disabled.
163 # executables and manpages, and some files are per-instance,
166 # of per-instance files.
168 # Before Postfix multi-instance support was implemented, the
170 # as part of the default Postfix instance.
172 # With multi-instance support, we simply continue to do this.
173 # Specifically, a Postfix instance will not check or update
174 # shared files when that instance's config_directory value is
179 # instance should be checked and updated before any other
184 # Only the multi-instance manager implements support for the
186 # multi-instance manager will start only Postfix instances
188 # setting of "no" allows a Postfix instance to be tested by
191 # The postfix(1) command operates on only one Postfix instance
201 # The multi-instance manager skips commands such as "stop"
202 # or "reload" that require a running Postfix instance, when
203 # an instance does not have "multi_instance_enable = yes".
206 # The multi-instance manager replaces a "start" command by
207 # "check" when a Postfix instance's main.cf file does not
209 # that problems will be reported even when the instance is
215 # value. Therefore, the default instance should be checked
228 # together with the default Postfix instance.
234 # only on the specified Postfix instance. This environment
247 # Postfix instance, and that are started, stopped, etc., together
248 # with the default Postfix instance.
250 # The pathname of a multi-instance manager command that the
254 # The optional instance name of this Postfix instance.
256 # The optional instance group name of this Postfix instance.
258 # Allow this Postfix instance to be started, stopped, etc., by a
259 # multi-instance manager.
273 # postmulti(1) full-blown multi-instance manager
274 # $daemon_directory/postfix-wrapper simple multi-instance manager