Michael Tokarev via Postfix-users:
> 09.12.2024 22:25, Wietse Venema via Postfix-users wrote:
> > Steffen Nurpmeso via Postfix-users:
> >> postfix_status() {
> >> # As postfix does not use stdout but console, no
> >> # postfix__init
> >> # ${prog} status 2>&1
> >
> > I think that was fixed in Postfix 3.8.
> >
> > 20230308
> >
> > Cleanup: the postfix(1) and postlog(1) commands now produce
> > stderr output even when stderr is not connected to a terminal.
> > This eliminates an inconsistency, and makes these programs
> > easier to use in some automated procedures. The canonical
> > example is to capture output from "postmulti -p status" to
> > figure out which instances are or are not running. Files:
> > postfix/postfix.c, postlog/postlog.c.
> The postlog manpage states:
> By default, logging is sent to syslogd(8) or postlogd(8); when
> the standard error stream is connected to a terminal, logging
> is sent there as well.
That text needs to be updated, because the stderr behavior has changed.
> I was confused by this description, while trying to understand why,
> when the system startup tools captures command output into logs,
> there are two messages produced:
>
> Dec 14 09:27:25 gandalf postfix[165466]: postfix/postlog: starting the
> Postfix mail system
> Dec 14 09:27:25 gandalf postfix/postfix-script[165466]: starting the Postfix
> mail system
>
> One is sent by postlog to the syslog, and another is captured from
> the stderr/out. It's an interesting effect.
Captured from stdout"? Tht is not happening in postfix-script. If
systemd is doing that, then I am not going to fight that.
Wietse
_______________________________________________
Postfix-users mailing list -- [email protected]
To unsubscribe send an email to [email protected]
