From owner-freebsd-current Tue Dec 24 17: 5:39 2002 Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 135DB37B401; Tue, 24 Dec 2002 17:05:39 -0800 (PST) Received: from mailman.zeta.org.au (mailman.zeta.org.au [203.26.10.16]) by mx1.FreeBSD.org (Postfix) with ESMTP id BF73443ED8; Tue, 24 Dec 2002 17:05:37 -0800 (PST) (envelope-from bde@zeta.org.au) Received: from katana.zip.com.au (katana.zip.com.au [61.8.7.246]) by mailman.zeta.org.au (8.9.3/8.8.7) with ESMTP id MAA32352; Wed, 25 Dec 2002 12:05:24 +1100 Date: Wed, 25 Dec 2002 12:07:27 +1100 (EST) From: Bruce Evans X-X-Sender: bde@gamplex.bde.org To: phk@freebsd.org Cc: current@freebsd.org Subject: bogus and/or broken sysctl kern.timecounter.tick Message-ID: <20021225115915.G19052-100000@gamplex.bde.org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG The kern.timecounter.tick sysctl is apparently intended to return the kernel variable `tc_tick' but actually returns the kernel variable `tick'. Returning `tick' is not useful since it is already returned in the currect place (the kern.clockrate sysctl). Returning `tc_tick' is apparently not useful either since apparently nothing cares about the wrong value being returned. Bruce To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message