Re: [runit/svlogd] RFE: periodic log-rotation; filter-malfunction

[Enrico Scholz <enrico.scholz@informatik.tu-chemnitz.de>]

pape@smarden.org (Gerrit Pape) writes:

>> Would it be possible to add another option (e.g. 'a<seconds>') which
>> sends SIGALRM at <seconds> seconds after the last logrotation?
>
> 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). Without looking at the code,
  I guess that an implementation in svlogd would be much smaller because
  the SIGALRM handler is already there.
  (Things are getting worse because I run 20-30 svlogd instances per
  machine in linux-vservers[1] (chroots, BSD-jail like))
* it requires additional software (svlogd is used without the other
  runit tools here) and setup.
* it would logrotate every buffer inclusive those which should not be
  touched (e.g. I have a local debug-buffer which I want to keep). 'a...' 
  could send a new signal (USR2??) which logrotates only the outdated
  buffers (I know that it conflicts with my initial idea...).


>> Another issue: the '-/+...' filters seem to fail sometimes.
> ...
> This shouldn't happen.  Can you please give an exact example of a line
> that ends up in the wrong log, copied and pasted, and also re-check that
> you post the exact contents of the config files?  Do you use the -r or
> -R command line options to svlogd in socklog-ucspi-tcp/log/run?

Please see http://www.tu-chemnitz.de/~ensc/runit/badfilter.txt

When you need de-anonymoused values, please contact me privatly.



Enrico

Footnotes: 
[1]  http://linux-vserver.org