From: Piotr Auksztulewicz <mlmmj-listrcpt@hasiok.net>
To: mlmmj@mlmmj.org
Subject: [mlmmj] Why different logging destinations
Date: Fri, 04 Nov 2016 17:07:50 +0000 [thread overview]
Message-ID: <20161104170750.GN15104@kibel.hasiok.net> (raw)
Hello all!
Just a thought: what's the reason for mlmmj executables using both
syslog (via the log_error() function) and a file in the list's spool
directory (mlmmj.operation.log, via the log_oper() function)? The latter
method also uses hardcoded log rotation logic. Also mlmmj-maintd logs
to a still different file, with its own rotation logic.
On top of that, some log_error()s look like debugs. I "love" this one
particularly:
Nov 2 18:15:02 hostname /usr/bin/mlmmj-process[16632]: mlmmj-process.c:839: Found Cc: user@example.com: Success
IMHO it would make more sense to log everything to syslog (falling back
to a file if syslog is not available) with different priorities, so
admins could apply filtering, routing and rotation to their tastes.
Currently I have to play tricks with syslog-ng to get all info into one
place, and it fails sometimes.
Greetings,
P.
--
Piotr "Malgond" Auksztulewicz firstname@lastname.net
reply other threads:[~2016-11-04 17:07 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20161104170750.GN15104@kibel.hasiok.net \
--to=mlmmj-listrcpt@hasiok.net \
--cc=mlmmj@mlmmj.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).