after network...

[Achim Gratz]

Udo van den Heuvel via devel writes:
> Can we please adjust the service files so that also ntp-wait.service
> starts after we have network?
> Currently only ntpd.service has references to network...

This is what I'm using on my two Tumbleweed machines (you may need to
adjust the installaion paths, some of them are nonstandard since I
compile ntpd myself and not using the packaged one):

ntpsec-steptime.service
-------------- next part --------------
A non-text attachment was scrubbed...
Name: ntpsec-steptime.service
Type: application/x-shellscript
Size: 480 bytes
Desc: not available
URL: <https://lists.ntpsec.org/pipermail/devel/attachments/20211120/d8109484/attachment.bin>
-------------- next part --------------

ntpsec-wait.service
-------------- next part --------------
A non-text attachment was scrubbed...
Name: ntpsec-wait.service
Type: application/x-shellscript
Size: 523 bytes
Desc: inline
URL: <https://lists.ntpsec.org/pipermail/devel/attachments/20211120/d8109484/attachment-0001.bin>
-------------- next part --------------

ntpsec-ntpd.service
-------------- next part --------------
A non-text attachment was scrubbed...
Name: ntpsec-ntpd.service
Type: application/x-shellscript
Size: 462 bytes
Desc: inline
URL: <https://lists.ntpsec.org/pipermail/devel/attachments/20211120/d8109484/attachment-0002.bin>
-------------- next part --------------

The first one gets the time within 100ms at least (on my network) and is
the only thing that could step the time.  Even if something else goes
wrong later the date / time will not be set wildly wrong (GPS having a
hiccup or network dropping out).  I let the boot process wait until the
time is synchronized, which usually takes about 16?18 seconds (in my
case it would not be necessary to do this).


Regards,
Achim.
-- 
+<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+

SD adaptation for Waldorf microQ V2.22R2:
http://Synth.Stromeko.net/Downloads.html#WaldorfSDada