El jue., 27 dic. 2018 a las 6:36, Dmitry Bogatov escribió:
>
> And this issue happens not only on crash, it happens after every
> termination of svlogd, due any signal. I would agree that SIGKILL is
> crash, but issue reproduces with SIGINT and SIGTERM.
SIGTERM should make svlogd exit cleanly,
Laurent Bercot:
If loggers kept appending to "current" instead, it could have corrupt
information in the middle of a "current" file, which would them be
archived as a .s (intact file), which wouldn't be good.
Examples:
* https://unix.stackexchange.com/questions/237321/
*
El jue., 27 dic. 2018 a las 10:47, Steve Litt escribió:
>
> [...] Simply run a program, invoked by cron,
> that deletes .u files over a certain age, as long as it doesn't delete
> the latest .u file.
Daemontools-style loggers like svlogd delete files themselves during a
rotation for a reason,..
[2018-12-26 00:05] Steve Litt
> part text/plain1664
> On Tue, 25 Dec 2018 13:39:17 +
> Dmitry Bogatov wrote:
>
> > Hello!
> >
> > I am Debian maintainer of `runit' supervision suite. Recently, I
> > received bug report [^1] about stray .u logfiles. After some
> >
[2018-12-26 03:58] Alex Efros
> Hi!
>
> I'm not sure is it good idea to include .u files in usual rotation process
> at all, and especially handle them just like .s files. If several crashes
> happens for some reason in a short period of time this will result in
> deletion of all log files
Why would it be wrong to just keep appending to `current' instead of
moving it to `.u' file? (see my patch at end of bug thread)
On a crash, it is possible that a file you're writing to gets
corrupted. For the integrity of your logs, it's better to move that
potentially corrupted file to
Alex Efros:
I'm not sure is it good idea to include .u files in usual rotation
process at all, and especially handle them just like .s files. If
several crashes happens for some reason in a short period of time this
will result in deletion of all log files except last (say) 10 .u
files,
