From: Michael Olbrich <m.olbrich@pengutronix.de>
To: ptxdist@pengutronix.de
Subject: Re: [ptxdist] Chrony has NTP capability disabled by default, why ?
Date: Fri, 24 Jul 2020 09:45:28 +0200 [thread overview]
Message-ID: <20200724074528.GA31910@pengutronix.de> (raw)
In-Reply-To: <CAH+2xPDAFGFAUhTLPVvv0pXVS_z+3ZOEXPxwh9WxkWdCxofHHQ@mail.gmail.com>
On Wed, Jul 22, 2020 at 08:44:55AM +0200, Bruno Thomsen wrote:
> Den tir. 21. jul. 2020 kl. 17.57 skrev Mircea Ciocan <m.ciocan@ppc-ag.de>:
> > Dear ptxdist developers (and especially Michael O.),
> >
> > we've had a head scratching session today, we've tried to use chrony as
> > a NTP server and for a number of hours was failing miserably, until
> > we've discovered that by default the NTP is disabled via
> > "non-bypassable" compilation switches given in the rule file, that is
> > "--disable-ntp", making it mostly useless :( .
>
> Hi Mircea
>
> I can see we have a local patched version that also removes --disable-ntp,
> and also adds systemd support, run as non-root user, version bump,
> authentication support option and custom start option.
Please send patches :-)
> > That is commit bd721be68 (Michael Olbrich 2018-06-02) and I was
> > wondering, is it chrony used so much without NTP functionality that by
> > default it was considered a good idea to be disabled, or what could be
> > the reason behind this ? Am I missing something obvious here ?
I don't actually remember, but I guess it wasn't needed at the time. Or
simply a mistake.
> > And also, for the people that uses chrony as a replacement for the old
> > ntpd, could we at least have a configuration switch/variable, defined in
> > the next version, to select this functionality if needed ?
>
> A switch would be fine in case some doesn't need ntp support.
I think ntp support can be enabled unconditionally. It doesn't look like it
needs extra dependencies, right?
> I should probably put together some patches with our local changes.
Yes please.
Michael
--
Pengutronix e.K. | |
Steuerwalder Str. 21 | http://www.pengutronix.de/ |
31137 Hildesheim, Germany | Phone: +49-5121-206917-0 |
Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917-5555 |
_______________________________________________
ptxdist mailing list
ptxdist@pengutronix.de
To unsubscribe, send a mail with subject "unsubscribe" to ptxdist-request@pengutronix.de
prev parent reply other threads:[~2020-07-24 7:45 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-21 15:57 Mircea Ciocan
2020-07-22 6:44 ` Bruno Thomsen
2020-07-24 7:45 ` Michael Olbrich [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20200724074528.GA31910@pengutronix.de \
--to=m.olbrich@pengutronix.de \
--cc=ptxdist@pengutronix.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox