[pkg-ntp-maintainers] [pkg-ntp] 04/13: Build sntp
Kurt Roeckx
kurt at roeckx.be
Sun May 7 21:00:37 UTC 2017
On Sun, May 07, 2017 at 10:47:00PM +0200, Bernhard Schmidt wrote:
> On 07.05.2017 22:30, Kurt Roeckx wrote:
> > On Sun, May 07, 2017 at 07:44:06PM +0000, Bernhard Schmidt wrote:
> >> diff --git a/debian/ntp.install b/debian/ntp.install
> >> index af7071d..a794f1b 100644
> >> --- a/debian/ntp.install
> >> +++ b/debian/ntp.install
> >> @@ -7,6 +7,7 @@ debian/tmp/usr/sbin/ntp-keygen
> >> debian/tmp/usr/sbin/ntp-wait
> >> debian/tmp/usr/sbin/ntpd
> >> debian/tmp/usr/sbin/ntptime
> >> +debian/tmp/usr/sbin/sntp
> >
> > It's probably more useful in it's own binary package.
> >
> > I'm wondering if we should run it fron crom / systemd trigger
> > with a random delay (like certbot does for instance), and we
> > should probably make it confict with the ntp package in that
> > case. An other alternative is that we make it act more like
> > like ntpdate.
>
> I'd like to have it co-installable, but maybe we could have both? A
> seperate sntp binary package, and a sntp-systemd (or -periodic or
> whatever) depending on sntp and conflicting with ntp (either the package
> or some runtime inhibition) shipping the necessary bits for a periodic
> SNTP sync?
That works for me too. I guess some poeple would like to use it as
a debug tool.
It would also need a list of servers, which we can probably put
in /etc/default/sntp
Kurt
More information about the pkg-ntp-maintainers
mailing list