From mboxrd@z Thu Jan 1 00:00:00 1970 Return-path: Received: from dude02.hi.pengutronix.de ([2001:67c:670:100:1d::28]) by metis.ext.pengutronix.de with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1jysOW-0008Fy-EG for ptxdist@pengutronix.de; Fri, 24 Jul 2020 09:45:28 +0200 Received: from mol by dude02.hi.pengutronix.de with local (Exim 4.92) (envelope-from ) id 1jysOW-0007xL-5k for ptxdist@pengutronix.de; Fri, 24 Jul 2020 09:45:28 +0200 Date: Fri, 24 Jul 2020 09:45:28 +0200 From: Michael Olbrich Message-ID: <20200724074528.GA31910@pengutronix.de> References: MIME-Version: 1.0 Content-Disposition: inline In-Reply-To: Subject: Re: [ptxdist] Chrony has NTP capability disabled by default, why ? List-Id: PTXdist Development Mailing List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Reply-To: ptxdist@pengutronix.de Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Errors-To: ptxdist-bounces@pengutronix.de Sender: "ptxdist" To: ptxdist@pengutronix.de On Wed, Jul 22, 2020 at 08:44:55AM +0200, Bruno Thomsen wrote: > Den tir. 21. jul. 2020 kl. 17.57 skrev Mircea Ciocan : > > 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