Bill Cole wrote in
<9132a300-ce42-4af6-bde5-023b47187...@billmail.scconsult.com>:
|On 2023-03-02 at 14:13:24 UTC-0500 (Thu, 02 Mar 2023 20:13:24 +0100)
|Steffen Nurpmeso <stef...@sdaoden.eu>
|is rumored to have said:
|
|> I do not think this has been reported already, on systems which
|> use GNU grep(1) postfix produces obsoletion messages.
|>
|> $ egrep x y
|> egrep: warning: egrep is obsolescent; using grep -E
|
|It cannot be Postfix's fault that your particular 'egrep' is
|self-deprecating.
|
|Not all implementations of egrep do that. Use a quieter one that you
|prefer, if the message disturbs you.
Some people are not only bugged, but change packages etc, for
example [1]
+
+ sed -i -e 's,egrep,grep -E,g' $PKG/usr/lib/postfix/postfix-{,tls-}script
[1]
https://crux.nu/gitweb/?p=ports/opt.git;a=commitdiff;h=9abc4acf99d1c3f41cfc5968ee1df45fdc8ab285
Also /var/log/messages from "somewhere", which is locatable for my
sequential daemon startup script
Feb 27 17:46:24 (none) /root/bin/net-qos.sh/START: Daemon postfix starting
Feb 27 17:46:24 (none) /root/bin/net-qos.sh/START: In startup; postfix is
picky, sleeping 5 to let devices settle
Feb 27 17:46:24 (none) /root/bin/net-qos.sh/START: egrep: warning: egrep is
obsolescent; using grep -E
but that may not be true on boxes with massively async startup.
--Steffen Schönbein
