Wietse Venema:
> Wietse Venema:
> > A. Schulze:
> > > Am 04.04.2018 um 19:08 schrieb Wietse Venema:
> > > > Eray Aslan:
> > > >> On Tue, Apr 03, 2018 at 07:46:42PM -0400, Wietse Venema wrote:
> > > >>> I updated both the postfix-script file and the master daemon.
> > > >>>
> > > >>> I'd appreciate it if someone could verify that this will run the
> > > >>> master daemon with PID 1, and that 'postfix stop' in the container
> > > >>> will stop the master daemon. If it doesn't, then Linux does weird
> > > >>> stuff with PID 1 processes.
> > >
> > > I found the same...
> > >
> > > > Just for the heck of it, can you replace in src/master/master_sig.c
> > > > this code:
> > > >
> > > > if (kill(pid, SIGKILL) < 0)
> > > > msg_fatal("%s: kill myself: %m", myname);
> > > >
> > > > With this code:
> > > >
> > > > exit(0);
> > > >
> > > > And see if that fixes the PID=1 behavior?
> > >
> > > it does in any way. Thanks, Wietse!
> > >
> > > I tried both, exit(0) and _exit(0) :-)
> >
> > Andreas, thanks for the encouraging words :-)
>
> I also need you guys to verify that with the Postfix master running
> as PID=1, "docker stop" will no longer leave the master daemon
> running until Docker times out and forcibly terminates everything.
>
> By default, "docker stop" should send signal SIGTERM (signal 15) which
> is what Postfix expects, but it is good to verify.
BTW postfix-3.4-20180404 has the _exit() call.
Wietse
