Am 02.04.2018 um 19:30 schrieb Wietse Venema:
> - "") exec $daemon_directory/master
> + "") exec $daemon_directory/master -d
> + $FATAL "could not start-fg $daemon_directory/master"
version 3.3.0 don't contain the "exec $daemon_directory/master" but only
"$daemon_directory/master"
anyway, the patched version run master as PID 1. fine!
root@postfix:/# ps afx
PID TTY STAT TIME COMMAND
336 pts/0 Ss 0:00 /bin/bash
342 pts/0 R+ 0:00 \_ ps afx
1 ? Ss 0:00 /usr/lib/postfix/master -d
334 ? S 0:00 pickup -l -t unix -d -u
335 ? S 0:00 qmgr -l -t unix -d -u
or from outside/docker host:
23584 ? Ssl 0:00 \_ docker-containerd --config /var/run/docker/contai
23794 ? Sl 0:00 \_ docker-containerd-shim -namespace moby -workd
23811 ? Ss 0:00 \_ /usr/lib/postfix/master -d
24193 ? S 0:00 \_ pickup -l -t unix -d -u
24194 ? S 0:00 \_ qmgr -l -t unix -d -u
But "docker stop $postfix_container" don't let exit master:
23584 ? Ssl 0:00 \_ docker-containerd --config /var/run/docker/contai
23794 ? Sl 0:00 \_ docker-containerd-shim -namespace moby -workd
23811 ? Ss 0:00 \_ /usr/lib/postfix/master -d
I tried "postfix stop" inside the container. That also terminate all child
processes but not the master itself.
So a container receiving "stop", still run with only master as PID 1
expected: master process exit and container terminate.
that's better then without the patch as postfix processes are shut down more
properly...
> See what happens with 'postfix stop' and if it kills too much.
in a container it don't hurt: there is nothing other
Andreas
