Dan Mahoney via Postfix-users:
> All,
>
> This is the most minor problem, but I'll bring it up.
>
> We use Lets Encrypt for our certs (using the Dehydrated client),
> and call a 'postfix reload' as part of the hook script if a cert
> has been renewed.
>
> We also wrapper this with ?cronic' which works not under the old
> cron principle that 'all cron jobs should be silent and output
> only in an error' (which means by the time you've got an error,
> you've lost context), but instead, that you'll get all a script's
> output if it either exits with a bad error code, *or* writes to
> stderr.
>
> So the issue:
>
> When calling 'postfix reload', should "postfix/postfix-script:
> refreshing the Postfix mail system" be written to stderr? It's
> not an error, and it feels like this message should go to stdout,
> or that there should be a command-line option to suppress non-error
> messages.
>
> Obviously, in my hook script, I can redirect stderr to /dev/null,
> but this means I might miss 'real' errors.
If the output bothers you, use grep.
postfix reload 2>&1 | grep -v "refreshing the Postfix mail system"
In the past people have complained that Postfix programs produced
NO OUTPUT when not run from a terminal. So now we have a luxury
problem of output where it is not desired.
Wietse
_______________________________________________
Postfix-users mailing list -- postfix-users@postfix.org
To unsubscribe send an email to postfix-users-le...@postfix.org
