From: Alex Efros <powerman@powerman.name>
To: supervision@list.skarnet.org
Subject: Re: Log rotation issue with runit
Date: Tue, 25 Dec 2018 16:57:55 +0200 [thread overview]
Message-ID: <20181225145755.GF29946@home.lan> (raw)
In-Reply-To: <E1gbmvX-0003Sd-0r@eggs.gnu.org>
Hi!
On Tue, Dec 25, 2018 at 01:39:17PM +0000, Dmitry Bogatov wrote:
> Recently, I received bug report [^1] about stray .u logfiles. After
> some investigation I found code, that caused issue, but it seems that it
> was written with some purpose, yet I fail to understand that purpose.
>
> [^1] https://bugs.debian.org/916230
.u files are created after svlogd crash (actually, when svlogd starts
again after crash). I don't think I've ever seen actual crash of svlogd,
so usually it means system was rebooted because of kernel OOPS or pressing
reset button or power loss or someone has killed svlogd with SIGKILL.
I believe this isn't a bug, but this behaviour isn't documented in svlogd
man page. To me it looks useful to be able to detect such crash-reboots
and what happens just before by looking for/in .u files.
--
WBR, Alex.
next prev parent reply other threads:[~2018-12-25 14:57 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-25 13:39 Dmitry Bogatov
2018-12-25 14:57 ` Alex Efros [this message]
2018-12-25 18:17 ` Guillermo
2018-12-25 18:30 ` Guillermo
2018-12-26 1:58 ` Alex Efros
2018-12-27 9:36 ` Dmitry Bogatov
2018-12-27 11:41 ` Laurent Bercot
2018-12-28 6:47 ` Jonathan de Boyne Pollard
2018-12-27 13:47 ` Steve Litt
2018-12-28 1:27 ` Guillermo
2018-12-27 23:39 ` Guillermo
2018-12-29 18:33 ` Dmitry Bogatov
2018-12-29 22:32 ` Guillermo
2018-12-28 6:57 ` Jonathan de Boyne Pollard
2018-12-26 5:05 ` Steve Litt
2018-12-27 9:36 ` Dmitry Bogatov
2018-12-27 13:07 ` Steve Litt
2018-12-29 18:33 ` Dmitry Bogatov
2018-12-30 1:20 ` Steve Litt
2018-12-30 10:04 ` Jonathan de Boyne Pollard
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=20181225145755.GF29946@home.lan \
--to=powerman@powerman.name \
--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).