15.12.2024 14:33, Viktor Dukhovni via Postfix-users wrote:
On Sun, Dec 15, 2024 at 11:34:54AM +0100, Tomasz Pala via Postfix-users wrote:
System-wide "defaults to 10000 messages in 30s" and "is applied per-
service", so this can be easily resolved by providing postfix.service
with:
LogRateLimitIntervalSec=0
Aha.
Nice in theory, but neither Wietse nor I distribute systemd service
definition files, and the ones in wide use don't do that.
I think this very important to understand possible issues and have
a fix. I can definitely fix this in debian - if I knew the problem
*exists* in the first place (I weren't aware *at all*, this is why
I asked).
This reminds me another issue frequently reported in debian: for example,
ldap: map does not work in debian because of the chroot (please keep
chroot question out of this thread, it's a separate issue, I'm just
stating the fact multiple reports has been made). And people start
adding various files (certs, libs, /etc/services, even keys for sasl
auth, etc) to chroot. But the solution is here for many years, and
it has been designed especially for this purpose: it is proxy: map
type. Do not endlessly try to copy more and more files into chroot,
use already available tools designed especially for this purpose,
which makes things easy.
However, I think that on a really busy server, the logging really can
go to a file directly, bypassing any log daemons, - maybe this is where
postlogd is actually helpful - not because of systemd/journald, but
because the volume of logs can be rather huge. Dunno, I haven't
thought about this aspect.
So, one prob is the rate limiting, which is easy to solve. I'm not
yet sure the limit should be upped by default though - again,
I just haven't thought about this so far.
stream rather than datagram based (separate stream per-process), and so
gets the logs out of order when logs are sent in close succession by
multiple processes.
Proper ordering is supposed to be one of the journald promises - are you
talking about stdout/stderr capture (I guess no), or /dev/log handling?
It fails when there are multiple coöperating processes doing the
logging. Precisely because a stream socket is chosen.
Interesting. I want to have a closer look. Thank you for the hints.
The vital part is to know what problems do we have :)
Thanks,
/mjt
_______________________________________________
Postfix-users mailing list -- postfix-users@postfix.org
To unsubscribe send an email to postfix-users-le...@postfix.org
