supervision - discussion about system services, daemon supervision, init, runlevel management, and tools such as s6 and runit
 help / color / mirror / Atom feed
From: Gerrit Pape <pape@smarden.org>
Subject: Re: [runit/svlogd] RFE: periodic log-rotation; filter-malfunction
Date: Mon, 18 Oct 2004 17:18:32 +0000	[thread overview]
Message-ID: <20041018171809.22727.qmail@0e94f701020d31.315fe32.mid.smarden.org> (raw)
In-Reply-To: <87sma1dmfu.fsf@kosh.ultra.csn.tu-chemnitz.de>

On Thu, Sep 02, 2004 at 11:55:49AM +0200, Enrico Scholz wrote:
> 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?

While re-reading this thread I tend to agree that this could be a
valuable feature.  Using a signal shouldn't be necessary when making it
a config option.

Regards, Gerrit.


      parent reply	other threads:[~2004-10-18 17:18 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-09-02  9:55 Enrico Scholz
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 [this message]

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=20041018171809.22727.qmail@0e94f701020d31.315fe32.mid.smarden.org \
    --to=pape@smarden.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 NNTP newsgroup(s).