On Sun, Mar 10, 2019 at 01:11:46AM -0800, Rick Thomas wrote: > Package: ntpsec > Version: 1.1.3+dfsg1-2 > Severity: important > > Dear Maintainer, > > *** Reporter, please consider answering these questions, where appropriate *** > > * What led up to the situation? > the /etc/ntpsec/ntp.conf file (attached) has two "pool" directives and no > "server" directives. > So it requires DNS (hence network services) to find out the IP addresses it > needs for servers. > DNS fails on the first "peer" and (for some reason) succeeds on the second > "peer". > If ntpsec implemented the "preempt" option on "peer" directives, the first > "peer" would be > revisited after a few minutes and all would be well. But it doesn't. So the > first "peer" > is as if it never existed. > * What exactly did you do (or not do) that was effective (or ineffective)? > Wait several seconds after boot completes then issue "sudo service ntpset > restart" > * What was the outcome of this action? > This time around, it sees both sets of "peers". > * What outcome did you expect instead? > I would have hoped that the systemd stuff would wait until DNS was available > before starting up ntpsec. > Unfortunately, I don't know systemd configuration well enough to suggest a > patch.
Hi Rick, Reading through the systemd network.target documentation here [1] (but also being somewhat new to it myself), I wonder if the behavior would work for your case if the Debian package changed: WantedBy=network-pre.target to After=network-online.target Wants=network-online.target in the unit file [2]. Would you be willing to test with that configuration? Thank you, tony [1] https://www.freedesktop.org/wiki/Software/systemd/NetworkTarget/ [2] https://github.com/rlaager/ntpsec-pkg/blob/sid/debian/ntpsec-systemd-netif.path#L9
signature.asc
Description: PGP signature
