From mboxrd@z Thu Jan 1 00:00:00 1970 From: "L. A. Walsh" Subject: Re: Question regarding ntpd Date: Mon, 10 Oct 2016 14:48:23 -0700 Message-ID: <57FC0CA7.4000404@tlinx.org> References: <6969452.IzX1pIz0vM@x2> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; Format="flowed" Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <6969452.IzX1pIz0vM@x2> List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: linux-audit-bounces@redhat.com Errors-To: linux-audit-bounces@redhat.com To: Steve Grubb Cc: linux-audit@redhat.com, "Jarsulic, Michael [CRI]" List-Id: linux-audit@redhat.com Steve Grubb wrote: > But ntpd overwhelms logs but chronyd might be marginally better. See bz > https://bugzilla.redhat.com/show_bug.cgi?id=918127 > --- I took a gander at said bugzilla num, and found a minor surprise in that there Miroslav Lichvar said: "You can use ntpd from the ntp package instead of chrony, it shouldn't call adjtimex as often as chronyd does." --- I.e. the exact opposite of your (Steve)'s statement. Wondered if that was a misread or newer information...<*idle curiosity*>. Either way sounds like it would be "nice" to differentiate a "read" from a "write" in this syscall if it is to be useful. -l