chronyd.service lists: After=ntpdate.service sntp.service ntpd.service Conflicts=ntpd.service why ntpd.service is in both After and Conflicts? Shouldn't chronny be specified to start after network is up through network.service of NetworkManager.service?
After=ntpd.service is needed to not start chronyd before ntpd exited. Without it "systemdctl start chronyd" when ntpd was running sometimes failed as chronyd tried to bind to port 123 before ntpd released it. According to the following document, network.service is not really useful here. http://www.freedesktop.org/software/systemd/man/systemd.special.html Does it cause any problems for you?
Interesting read, thanks. I don't see any problems. But reading http://www.freedesktop.org/wiki/Software/systemd/NetworkTarget/ it seems to me chronyd is good to have After=network.target I read it like that.
I'm not sure. To me it looks like adding After=network.target won't make a difference as chronyd is using UDP only and can be stopped after network, it shouldn't really matter.
If there are no TCP connections used, then you are right.
Ok, I'm closing this bug. If there are any cases where the dependency on the network target would be useful, please reopen.