From owner-freebsd-current Sat May 9 14:19:16 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA02668 for freebsd-current-outgoing; Sat, 9 May 1998 14:19:16 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from khavrinen.lcs.mit.edu (khavrinen.lcs.mit.edu [18.24.4.193]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA02646 for ; Sat, 9 May 1998 14:19:02 -0700 (PDT) (envelope-from wollman@khavrinen.lcs.mit.edu) Received: (from wollman@localhost) by khavrinen.lcs.mit.edu (8.8.8/8.8.8) id RAA10371; Sat, 9 May 1998 17:18:53 -0400 (EDT) (envelope-from wollman) Date: Sat, 9 May 1998 17:18:53 -0400 (EDT) From: Garrett Wollman Message-Id: <199805092118.RAA10371@khavrinen.lcs.mit.edu> To: Harlan Stenn Cc: Andreas Klemm , current@FreeBSD.ORG Subject: Re: should we update xntp in the base system to newest ntp version ? In-Reply-To: <29486.894399377@brown.pfcs.com> References: <19980505175215.A3650@klemm.gtn.com> <29486.894399377@brown.pfcs.com> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG < said: > I'd like to see the current xntp upgraded to ntp4 (or even ntp3, if that's > as far as folks are willing to go). We should have updated to 3-5.9x a long time ago. My fault. I tried running one of the early 4s a couple of months ago and it kept crashing. My suggestion would be up to update to the last xntp3 release (which can be done using the current build structure, leaving potential contribification for ntp4 so that we'll have less junk in the attic). -GAWollman -- Garrett A. Wollman | O Siem / We are all family / O Siem / We're all the same wollman@lcs.mit.edu | O Siem / The fires of freedom Opinions not those of| Dance in the burning flame MIT, LCS, CRS, or NSA| - Susan Aglukark and Chad Irschick To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message