supervision - discussion about system services, daemon supervision, init, runlevel management, and tools such as s6 and runit
 help / color / mirror / Atom feed
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: Sat, 29 Dec 2018 18:33:06 +0000	[thread overview]
Message-ID: <E1gdJQ3-0003hp-Gg@eggs.gnu.org> (raw)
In-Reply-To: <20181227080707.099b9c75@mydesk.domain.cxm>

[2018-12-27 08:07] Steve Litt <slitt@troubleshooters.com>
> > [ Dmitry Bogatov ]
> > No, it is reproducible. See end of bug thread.
> 
> Hi Dmitry,
> 
> Just so we're all on the same page, do you mean the end of
> https://bugs.debian.org/916230 ? Could you please provide a message
> number? I briefly looked over https://bugs.debian.org/916230, paying
> particular attention to the later half, and could see no reproduction
> sequence articulated. But sometimes I miss things.

Sure. Message 17:

 Offending .u file is created by rename(2) call at line 532, in
 logdir_open() function. It happens, when 'current' file exists,
 non-executable and non-empty.
 [...]


  reply	other threads:[~2018-12-29 18:33 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
2018-12-27 13:07     ` Steve Litt
2018-12-29 18:33       ` Dmitry Bogatov [this message]
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=E1gdJQ3-0003hp-Gg@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).