From: Dmitry Bogatov <KAction@debian.org>
To: Steve Litt <slitt@troubleshooters.com>
Cc: supervision@list.skarnet.org
Subject: Re: Log rotation issue with runit
Date: Thu, 27 Dec 2018 09:36:27 +0000 [thread overview]
Message-ID: <E1gcS5b-0001Od-QF@eggs.gnu.org> (raw)
In-Reply-To: <20181226000505.1e82b362@mydesk.domain.cxm>
[2018-12-26 00:05] Steve Litt <slitt@troubleshooters.com>
> part text/plain 1664
> On Tue, 25 Dec 2018 13:39:17 +0000
> Dmitry Bogatov <KAction@debian.org> wrote:
>
> > Hello!
> >
> > I am Debian maintainer of `runit' supervision suite. 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.
> >
> > Author Gerrit Pape directed me here. Any clarification would be
> > welcome! Please keep bug in thread.
> >
> > [^1] https://bugs.debian.org/916230
> [...]
>
> This seems to be an intermittent problem (not reproducible at will),
> and very hard to reproduce by anyone but the bug reporter. If the
> preceding sentence is true, it's possible it will never be solved. In
> such a situation, a workaround becomes a legitimate tactic.
No, it is reproducible. See end of bug thread.
next prev parent reply other threads:[~2018-12-27 9:36 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
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 [this message]
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=E1gcS5b-0001Od-QF@eggs.gnu.org \
--to=kaction@debian.org \
--cc=slitt@troubleshooters.com \
--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).