Why ntpd started so late after boot?

I start a custom app in rc.local, which is started by S95done. However, there is a good chance that the system time is not accurate in this moment, as ntpd is started as S98sysntpd, later on.
Can't the time be set earlier, just after net ?

Which leads to the question of synchroneous execution of the scripts in /etc/rc.d, but that is another (unfortunate) issue.

(Actually, I do a ntpd -q before starting my app in rc.local, as a "brutal" workaround.)

Hm, I don't think there is a particular reason for the high start index. However moving it right after network would not really help as ntpd is started in background and requiring quite some time to actually sync.

Maybe consider using a hotplug handler in /etc/hotplug.d/ntp/ instead of hoping for the /etc/rc.local timing to be correct.