Adrian Chadd:
[...] the uptime stuff really threw us.
It's unfair to lay such system time problems at s6's door. Systems whose
system clock jumps 46 years during system bootstrap don't get to blame
s6 for mad time gaps that appear in logs and service start time
records. There is a *lot* of
Adrian Chadd:
Sure, but I'm looking for something more generic than just devd. Like,
notifications about events like "default route is up" can be done by
sniffing the rtsock, but notifications like "ntpdate has updated the
date, we can now do crypto services" doesn't happen there right now.
Jonathan de Boyne Pollard:
What are these Linuxisms in s6? s6-linux-utils and s6-linux-init have
Linuxisms, obviously. But what Linuxisms does s6 have?
Adrian Chadd:
We just had a bunch of fun trying to get it to build right, [...]
Such as what, specifically?
f the arcane bits to get logging working right.
What are these Linuxisms in s6? s6-linux-utils and s6-linux-init have
Linuxisms, obviously. But what Linuxisms does s6 have?
We just had a bunch of fun trying to get it to build right, and the
uptime stuff really threw us.
It's fine though, I
(Answering to Jan here, but the "you" in this message is generic - if
anything, it's directed more at Adrian.)
On 25/08/2016 11:56, Jan Bramkamp wrote:
The skalibs library used by s6 to calculate the deadlines
should use clock_gettime(CLOCK_MONOTONIC) on FreeBSD and
as such shouldn't be
, and the lack of sensible time code in it
(its calculations for daemon run duration is based on system time, not
wall clock, so if your box boots jan 1, 1970 then gets NTP, things
are.. hilarious), and some of the arcane bits to get logging working
right.
What are these Linuxisms in s6? s6-linux
calculations for daemon run duration is based on system time, not
wall clock, so if your box boots jan 1, 1970 then gets NTP, things
are.. hilarious), and some of the arcane bits to get logging working
right.
What are these Linuxisms in s6? s6-linux-utils and s6-linux-init have
Linuxisms, obviously
