supervision - discussion about system services, daemon supervision, init, runlevel management, and tools such as s6 and runit
 help / color / mirror / Atom feed
From: Guillermo <gdiazhartusch@gmail.com>
To: Supervision <supervision@list.skarnet.org>
Subject: Re: Following log directories
Date: Sun, 28 Jun 2020 16:38:50 -0300	[thread overview]
Message-ID: <CADQ2Nw_uzgwAk1zLiKkix35fMwBdhzgt8FMVdvgWb8b9nkYLmQ@mail.gmail.com> (raw)
In-Reply-To: <435fd503-b57c-41a4-02ec-2a7d0ea229e1@NTLWorld.COM>

El sáb., 27 jun. 2020 a las 4:59, Jonathan de Boyne Pollard escribió:
>
> John W Higgins wrote:
>
> > I meant nothing towards s6 - but daemontools does not deal with leap
> > seconds (or at least it cetainly looks that way from my foolish
> > viewpoint).
> >
> daemontools very much *does* deal in leap seconds.  The little-known
> requirement for daemontools, which *is* in its manual and has been all
> along albeit that many people have overlooked this, is that one use one
> of the Olson "right" timezones.

If anyone is interested, decoding the TAI64N timestamps produced by
s6-log with nosh's version of tai64nlocal produces the same result as
doing so with s6-tai64nlocal, and decoding the TAI64N timestamps
produced by nosh's cyclog with s6-tai64nlocal produces the same result
as doing so with nosh's tai64nlocal. At least on my system without a
"right/" timezone.

On the other hand, I just realized that cyclog does not seem to
properly finalize the 'current' file (including the setting of the
execute-by-owner permission) when it exits normally. Perhaps the
destructor of class 'logger' should call logger::flush_and_close()
rather than logger::close()?

G.

  reply	other threads:[~2020-06-28 19:39 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-06-25  9:27 Carl Winbäck
2020-06-25 13:20 ` Guillermo
2020-06-25 14:52   ` Guillermo
2020-06-25 22:08     ` Carl Winbäck
2020-06-25 22:32       ` John W Higgins
2020-06-26  0:09         ` Laurent Bercot
2020-06-26  0:49           ` John W Higgins
2020-06-26  9:24             ` Jan Braun
2020-06-26  9:27             ` Laurent Bercot
2020-06-26 19:52               ` John W Higgins
2020-06-27  6:12                 ` Laurent Bercot
2020-06-27  7:33             ` Jonathan de Boyne Pollard
2020-06-28 19:38               ` Guillermo [this message]
2020-06-27  7:33         ` 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=CADQ2Nw_uzgwAk1zLiKkix35fMwBdhzgt8FMVdvgWb8b9nkYLmQ@mail.gmail.com \
    --to=gdiazhartusch@gmail.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).