supervision - discussion about system services, daemon supervision, init, runlevel management, and tools such as s6 and runit
 help / color / mirror / Atom feed
From: Charlie Brady <charlieb-smarden-supervision@budge.apana.org.au>
Cc: supervision@list.skarnet.org
Subject: Re: [runit/svlogd] RFE: periodic log-rotation; filter-malfunction
Date: Fri, 3 Sep 2004 11:15:48 -0400 (EDT)	[thread overview]
Message-ID: <Pine.LNX.4.44.0409031108200.11828-100000@e-smith.charlieb.ott.istop.com> (raw)
In-Reply-To: <87llfse3k2.fsf@kosh.ultra.csn.tu-chemnitz.de>


On Thu, 2 Sep 2004, Enrico Scholz wrote:

> > I'll have to think about it, in the meantime you could setup a separate
> > service doing this work, e.g.:
> >
> >  /var/service/socklogrotate/run:
> >  #!/bin/sh
> >  runsvctrl alarm /var/service/socklog
> >  exec sleep <seconds>
> 
> I do not like this, because:
> 
> * it adds extra bloat to the system (it is bad enough that I have to spawn
>   a stunnel-instance per logrotation; an additional sleep+bash-process
>   would increase system-load significantly).

You're running stunnel and bash (and probably SysVinit and xinetd), and
you point the bloat finger at one little runsv process?

If you want to start a new shell less frequently, do:

#!/bin/ash
while true
do
 runsvctrl alarm /var/service/socklog/log
 sleep <seconds>
done

If you want a small solution, write a small program which trickles "a" 
characters into the control fifo for socklog/log, then supervise it.

---
Charlie



  parent reply	other threads:[~2004-09-03 15:15 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 [this message]
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=Pine.LNX.4.44.0409031108200.11828-100000@e-smith.charlieb.ott.istop.com \
    --to=charlieb-smarden-supervision@budge.apana.org.au \
    --cc=supervision@list.skarnet.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).