Description:

Description:
When I want to run simultaneous ntpd.service and ntpdate.service on boot, so my system time will be quickly fixed and then ntpd will be keeping it accurate, one of them will fail, because ntpd exits when another instance is running and on systemd they will be started in parallel. Patch for ntpdate.service attached that sets strict run order.

This is a new issue for old bug (https://bugs.archlinux.org/task/34029, Allan asked me to reopen it as a new issue). I've encountered it outside of ARM world: on an old machine with a dead CMOS battery. This fix allows it to fix time quickly on boot and then continue maintaining it for a long term. Without it, time will either be quickly set by ntpdate (with ntp failing to start), or I'll have to wait for a minute or two till ntp sets correct time (with ntpdate failing).

Additional info:
* package version(s)
extra/ntp 4.2.6.p5-13
* config and/or log files etc.
Errors in "systemctl status ntpd.service" (instantly exits with code 0) --- when ntpdate started first.
No fixed time right after boot --- when ntpd started first.

Steps to reproduce:
1. Enable both ntpd.service and ntpdate.service
2. Reboot
3. Check services logs

Additional info:
* package version(s)
ntp 4.2.6.p5-18

Steps to reproduce:
1. Enable both ntpdate and ntp services.
2. Reboot.
3. Check status of both.