Hi all,
An mdoc(7) port of the documentation for s6-linux-init is now
available:
https://git.sr.ht/~flexibeast/s6-linux-init-man-pages/archive/v1.1.1.0.1.tar.gz
Alexis.
Hi all,
A new release of s6-rc-man-pages is now available:
https://git.sr.ht/~flexibeast/s6-rc-man-pages/archive/v0.5.4.1.2.tar.gz
It adds three section 7 pages:
* s6-rc-faq.7
* s6-rc-overview.7
* s6-rc-why.7
Alexis.
"Laurent Bercot" writes:
The way to go about it would be to implement the functionality
yourself, and submit a patch; that said, since the last time we
saw
svlogd's maintainer was four years ago in a flash
Well, Void maintains its own runit repo:
https://github.com/void-linux/runit
> Yes. You cannot set your system clock to TAI, unless you want wildly
> incorrect results from time() [...]
>
In my world time() returns the SI seconds since the start of 1970.
Since TAI and UTC were off for fractions of a second
from 1970 to the end of 1972 might be true,
but my applications
I don't know exactly what u mean with "TAI-10".
I guess u are refering to those 10seconds
Yes. You cannot set your system clock to TAI, unless you want wildly
incorrect results from time() and similar system calls. Setting it 10
seconds earlier than TAI is the best you can do; and that's what
Laurent Bercot wrote:
> If your system clock is set to TAI-10, [...]
>
I don't know exactly what u mean with "TAI-10".
I guess u are refering to those 10seconds
that were the initial difference between UTC and TAI at the start of 1972...
So it should be TAI-00:00:10...
> [...] then *all* the
My boxes use TAI (international atomic time) in order to have SI-seconds and
60sec minutes and 24hrs days...
If your system clock is set to TAI-10, then *all* the time-handling
software on your machine must be aware of it, in order to perform
time computations accurately. It is not sufficient
Hi!
My boxes use TAI (international atomic time) in order to have SI-seconds and
60sec minutes and 24hrs days... I do not like time jumps (exempli gratia: leap
seconds as "implemented" on many UN*X boxes...)... and Google's "smeared
time"... Details:
