From owner-freebsd-current Sat Jan 1 16:29: 4 2000 Delivered-To: freebsd-current@freebsd.org Received: from critter.freebsd.dk (critter.freebsd.dk [212.242.40.131]) by hub.freebsd.org (Postfix) with ESMTP id 815EC14D0B for ; Sat, 1 Jan 2000 16:28:55 -0800 (PST) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (localhost.freebsd.dk [127.0.0.1]) by critter.freebsd.dk (8.9.3/8.9.3) with ESMTP id BAA28368; Sun, 2 Jan 2000 01:28:44 +0100 (CET) (envelope-from phk@critter.freebsd.dk) To: Karl Denninger Cc: John Polstra , current@FreeBSD.ORG Subject: Re: xntpd - VERY old folks, how about updating? :-) In-reply-to: Your message of "Sat, 01 Jan 2000 18:25:18 CST." <20000101182518.A17456@Denninger.Net> Date: Sun, 02 Jan 2000 01:28:44 +0100 Message-ID: <28366.946772924@critter.freebsd.dk> From: Poul-Henning Kamp Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <20000101182518.A17456@Denninger.Net>, Karl Denninger writes: >> >options "P1003_1B" >> >options "_KPOSIX_PRIORITY_SCHEDULING" >> >options "_KPOSIX_VERSION=199309L" >> > >> >Current versions of ntpd use these features if they're available. I >> >think "_KPOSIX_VERSION=199309L" is the default, so that one probably >> >isn't strictly necessary. >> >> I seriously doubt using these will do anything for NTPDs performance. > >It won't, but it will stop ntpd from bitching in the syslog about them being >missing :-) Hm, I actually thought I managed to get somebody to solve that somehow, maybe I didn't quite succeed :-) -- Poul-Henning Kamp FreeBSD coreteam member phk@FreeBSD.ORG "Real hackers run -current on their laptop." FreeBSD -- It will take a long time before progress goes too far! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message