From owner-freebsd-questions@FreeBSD.ORG Mon Nov 3 21:59:31 2003 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 6F3F816A4CE for ; Mon, 3 Nov 2003 21:59:31 -0800 (PST) Received: from catseye.mine.nu (d154-5-164-0.bchsia.telus.net [154.5.164.0]) by mx1.FreeBSD.org (Postfix) with SMTP id 7D4B443FF3 for ; Mon, 3 Nov 2003 21:59:30 -0800 (PST) (envelope-from catseye@catseye.mine.nu) Received: (qmail 40453 invoked by uid 1001); 4 Nov 2003 06:02:11 -0000 Date: Mon, 3 Nov 2003 22:02:11 -0800 From: Chris Pressey To: "nw1" Message-Id: <20031103220211.254679db.cpressey@catseye.mine.nu> In-Reply-To: <008c01c3a291$83406920$0300a8c0@install> References: <008c01c3a291$83406920$0300a8c0@install> Organization: Cat's Eye Technologies X-Mailer: Sylpheed version 0.9.7 (GTK+ 1.2.10; i386-portbld-freebsd4.9) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit cc: trodat@ultratrends.com cc: freebsd-questions@freebsd.org Subject: Re: Overheating attributed to Freebsd --sysctl variablesnotavailable-- 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: Tue, 04 Nov 2003 05:59:31 -0000 On Tue, 4 Nov 2003 00:07:14 -0500 "nw1" wrote: > This does make absolute sense, but this isn't a publicly accessable > machine, so it would rarely reach that max_load to cause it to > overheat as its doing now, provided, I can find someone to answer the > second outstanding question; Where are those sysctl variables that i > was previously able to set? They are no longer available You know, it's a good question - just for kicks, I tried this on my two FreeBSD machines: FreeBSD 4.9-RC #1: Wed Oct 15 08:12:11 PDT 2003: # apm apm: can't open /dev/apm: Device not configured # sysctl machdep.apm_standby_delay machdep.apm_standby_delay: 1 FreeBSD 4.9-STABLE #1: Sat Nov 1 09:16:30 PST 2003: # apm APM version: 1.2 APM Management: disabled AC Line status: unknown (... etc ...) # sysctl machdep.apm_standby_delay sysctl: unknown oid 'machdep.apm_standby_delay' ...which is a bit odd, to say the least. If anything, I would've expected the machine that doesn't have APM support compiled in to the kernel, to be the one with no understanding of APM-related sysctls. But, it's the other way around. Maybe something changed in the last two weeks? But you're running 4.8-RELEASE-p13 - I'd expect that to be (essentially) older than either of my installations... Anyway, those two oids don't seem to be documented under sysctl(8). And googling on them doesn't yield a lot. I really have no idea, I just thought I'd throw this out there as another data point. (This issue seems to be generating more heat than light, if you'll pardon the pun :) -Chris