> >> On 12/19/2017 05:25 AM, Wietse Venema wrote:
> >>> As for forgrounding, this must happen only after the 'postfix
> >>> check' sanity checks and repairs complete sucessfully. Running a
> >>> 'bare' master daemon would violate design assumptions. So this
> >>> will require a new 'postfix' subcommand that starts exactly one
> >>> instance in the foreground.
This was implemented in Postfix 3.3.
Wietse
POSTFIX(1) POSTFIX(1)
NAME
postfix - Postfix control program
SYNOPSIS
postfix [-Dv] [-c config_dir] command
DESCRIPTION
...
start-fg
Like start, but keep the master daemon running in the fore-
ground. This requires that multi-instance support is disabled
(i.e. the multi_instance_directories parameter value must be
empty). When running Postfix inside a container, mount the con-
tainer host's /dev/log socket inside the container (example:
"docker run -v /dev/log:/dev/log ...") and specify a distinct
Postfix "syslog_name" prefix that identifies logging from the
Postfix instance.
