From: Enrico Scholz <enrico.scholz@informatik.tu-chemnitz.de>
Subject: [runit/svlogd] RFE: periodic log-rotation; filter-malfunction
Date: Thu, 02 Sep 2004 11:55:49 +0200 [thread overview]
Message-ID: <87sma1dmfu.fsf@kosh.ultra.csn.tu-chemnitz.de> (raw)
Hello,
I am using svlogd 1.0.2 + socklog 1.5.0 which are great programs. But I
miss a small feature: I am using network logging and have some hosts
with a small log-volume. On these, the logrotation (configured with
's4096') happens very seldom (perhaps 3-4 times per day) and I would
miss important messages when evaluating the logs on the loghost.
Because the transfer is expensive (piped into stunnel), and I want to
share the configuration with other hosts with a higher log-volume, I do
not want to play with the 's....' parameter.
Would it be possible to add another option (e.g. 'a<seconds>') which
sends SIGALRM at <seconds> seconds after the last logrotation?
Another issue: the '-/+...' filters seem to fail sometimes. E.g. I have
in main/config
| -*: @* mail.*: *
and in mail/config
| -*
| +*: @* mail.*: *
These rules are working the most time, but I see single message like
| @400000004136debc1e6b394c mailbox: @400000004136db9604ff84a4 mail.notice: Sep 2 10:36:28 imap[9964]: login: ...
in main/current. This message is missing in mail/current, but other ones
transfered in the same logrotation at 'mailbox' are in mail/current as
expected.
I guess this has something to do with wrapping buffers (mailbox has the
's4096' setting), but I can not give a reproducible example.
Enrico
next reply other threads:[~2004-09-02 9:55 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-09-02 9:55 Enrico Scholz [this message]
2004-09-02 19:48 ` Gerrit Pape
2004-09-02 19:53 ` Charlie Brady
2004-09-02 20:12 ` Gerrit Pape
2004-09-02 21:58 ` Enrico Scholz
2004-09-03 11:08 ` Gerrit Pape
2004-09-11 9:56 ` Gerrit Pape
2004-09-03 14:54 ` Joan Picanyol
2004-09-03 15:15 ` Charlie Brady
2004-10-18 17:18 ` Gerrit Pape
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=87sma1dmfu.fsf@kosh.ultra.csn.tu-chemnitz.de \
--to=enrico.scholz@informatik.tu-chemnitz.de \
/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 NNTP newsgroup(s).