[systemd-devel] [BUG] time-sync.target reached prematurely

Lukasz Stelmach stlman at poczta.fm
Tue Aug 26 13:11:29 PDT 2014


Greetings.

According to systemd.special(7) "all services where correct time is
essential should be ordered after" time-sync.target. Implicitly this
means that if systemd-timesyncd is enabled services ordered after the
target should also get a usable network connection because the daemon
uses the network (not a GPS receiver like ntpd could do) to synchronise
the clock. However, this isn't actually the case as systemd-timesyncd
reports "READY=1" [1] before even checking if network is online *and*
querying servers. The target is reached *before* time is synced.

How would you suggest to fix this?


Kind regards,

[1]
http://cgit.freedesktop.org/systemd/systemd/tree/src/timesync/timesyncd.c?id=36202fd2bc252616966166c98ccb0e0e5ece1fc9#n135
-- 
Było mi bardzo miło.                   Twoje oczy lubią mnie
>Łukasz<                                     i to mnie zgubi  (c)SNL

REKLAMA: http://ars-fabrica.eu/

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 538 bytes
Desc: OpenPGP digital signature
URL: <http://lists.freedesktop.org/archives/systemd-devel/attachments/20140826/704171ab/attachment.sig>


More information about the systemd-devel mailing list