On Mon, Dec 09, 2024 at 11:27:53AM +0300, Michael Tokarev via Postfix-users
wrote:
> If main.cf has multi_instance_enable=yes, and multi_instance_wrapper
> set, an instance becomes a multi-instance, and `postfix start` will
> run the multi_instance_wrapper instead of the usual postfix-script,
> so an instance automatically becomes a multi-instance using the regular
> postfix command.
>
> And this probably can be nested if needed, I guess, at least in the
> part when an instance is started with -c $config_directory - so a
> custom main.cf might be a multi-instance setup too, not just the
> main one - but I haven't verified this.
No, postmulti does not support nesting. It is expected that the content
of $meta_directory is not duplicated, and its correct location is set in
the default main.cf.
> So, if a distribution chooses to manage multiple instances in a form
> of, say, separate systemd units, - it looks like postmulti tool is
> not the right tool to use here, - regular `postfix' tool with -c (or
> $MAIL_CONFIG) is the way to go.
Correct, either "-c /etc/postfix" or MAIL_CONFIG=/etc/postfix (or
whatever the directory is in your build) is required to suppress
multi-instance startup when configured.
> In other words, a distribution (or a user) can choose to run multiple
> independent postfix instances using `postfix -c DIR` way, managing
> them as independent systemd units (or using other means) - this is
> multiple instances of user-kind. And each such independent user-kind
> postfix instance might be a multi-instance by its own internally,
No, none will be. With "-c /some/path" exactly that instance is
started.
--
Viktor.
_______________________________________________
Postfix-users mailing list -- postfix-users@postfix.org
To unsubscribe send an email to postfix-users-le...@postfix.org
