From owner-freebsd-questions@FreeBSD.ORG Fri Jan 21 23:47:15 2005 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id B6E5116A4CE for ; Fri, 21 Jan 2005 23:47:15 +0000 (GMT) Received: from jupiter.picknowl.com.au (jupiter.picknowl.com.au [203.87.94.38]) by mx1.FreeBSD.org (Postfix) with ESMTP id 24EDA43D55 for ; Fri, 21 Jan 2005 23:47:13 +0000 (GMT) (envelope-from imoore@picknowl.com.au) Received: from daemon.foo.lan (adsl-176-70.swiftdsl.com.au [218.214.176.70]) by jupiter.picknowl.com.au (Postfix) with ESMTP id 891DD96C93 for ; Sat, 22 Jan 2005 10:17:11 +1030 (CST) From: Ian Moore To: freebsd-questions@freebsd.org Date: Sat, 22 Jan 2005 10:17:04 +1030 User-Agent: KMail/1.7.2 References: <200501112100.10680.imoore@picknowl.com.au> <200501220015.57752.imoore@picknowl.com.au> <44651qsrc8.fsf@be-well.ilk.org> In-Reply-To: <44651qsrc8.fsf@be-well.ilk.org> MIME-Version: 1.0 Content-Type: multipart/signed; boundary="nextPart2761719.M8RlCuF0fc"; protocol="application/pgp-signature"; micalg=pgp-sha1 Content-Transfer-Encoding: 7bit Message-Id: <200501221017.10875.imoore@picknowl.com.au> Subject: Re: ntpd problems since upgrading to 5.3 - found the problem! X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 21 Jan 2005 23:47:15 -0000 --nextPart2761719.M8RlCuF0fc Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline On Sat, 22 Jan 2005 02:32, Lowell Gilbert wrote: > Ian Moore writes: > > On Wed, 19 Jan 2005 00:54, Lowell Gilbert wrote: > > > Ian Moore writes: > > > > I've just realised I'm not running a name server at all on my 5.3 > > > > system. I have 4.9 installed on this computer too & I'd set up the > > > > caching server on it, I guess I forgot that step when I installed > > > > 5.3. > > > > I'll set it up & see that makes any difference. > > > > > > Make sure to switch to using domain names that aren't in use by other > > > people... > > > > > > [A common convention is to use ".lan" or ".local" as the top-level > > > domain if you are using non-public domain names.] > > > > Thanks, I hadn't thought of using a non-existant top level domain. I've > > changed the hostname to daemon.foo.lan and now localhost.foo.lan resolv= es > > to 127.0.0.1 as it should. > > Unfortunately, I still get the same response form ntpq: > > daemon:~ % sudo ntpq -p > > ntpq: write to localhost.foo.lan failed: Permission denied > > Even with my firewall disabled I get this response. > > What about "ntpq -pn"? No, I get the same response from that too. Cheers, =2D-=20 Ian GPG Key: http://homepages.picknowl.com.au/imoore/imoore.asc --nextPart2761719.M8RlCuF0fc Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.0 (FreeBSD) iD8DBQBB8ZR+fITqkXhImmIRAgYMAKCNfOGhb/34PGVJTvUCdBN5EAiM6QCdH+n/ BieyFmXjatLDprhD+X/vRZQ= =GVqp -----END PGP SIGNATURE----- --nextPart2761719.M8RlCuF0fc--