Tomasz Pala via Postfix-users:
> > Again, what about the logging from NON-DAEMON Postfix processes
> > such as sendmail, postdrop, postqueue, and so on?
>
> They belong to their calling service. Therefore if I run sendmail from
> the shell, it belongs to my user's slice. If postdrop is run from
> mimedefang-multiplexor.service, it's accounted to mimedefang, not
> postfix.service.
>
> Excessive logging by some user won't impact another service.
>
> # echo | postdrop
> protocolpostdrop_protocolqueue_id03AD4840693postdrop: warning: stdin:
> unexpected EOF reading length, record type 10
> postdrop: fatal: uid=0: malformed input
>
> # journalctl -o json-pretty --since -2m
This assues that one already knows when some event of interest
happened.
> # journalctl -u session-c219.scope
This assumes that one aready knows what session scope to search for.
> # journalctl -u postfix | grep fatal
Right.
> # journalctl --identifier=postfix/postdrop
> # journalctl _EXE=/usr/sbin/postdrop
Both assume that one already knows the event of interest involved
the postdrop command.
Wietse
_______________________________________________
Postfix-users mailing list -- [email protected]
To unsubscribe send an email to [email protected]
