Date: Mon, 3 Nov 2003 22:09:56 -0500 From: "nw1" <network101@covad.net> To: "peter lageotakes" <plageotakes@yahoo.com>, "Jud" <judmarc@fastmail.fm> Cc: freebsd-questions@freebsd.org Subject: Re: Overheating attributed to Freebsd --sysctl variables notavailable-- Message-ID: <003e01c3a281$1fdb6a20$0300a8c0@install> References: <20031104003834.45540.qmail@web14609.mail.yahoo.com><000e01c3a26e$a5024ec0$0300a8c0@install> <oprx3ebfhn0cf2rk@mail.messagingengine.com>
next in thread | previous in thread | raw e-mail | index | archive | help
I'm interested in those missing sysctl variables I posted @ http://69.3.136.141/freebsd/installation/sysctl_variables_missing. Using a Third party application/script to fix something that was natively working or under control, I don't think, is the way to go and causes another level of complexity. Wouldn't you think? ----- Original Message ----- From: "Jud" <judmarc@fastmail.fm> To: "nw1" <network101@covad.net>; "peter lageotakes" <plageotakes@yahoo.com> Cc: <freebsd-questions@freebsd.org> Sent: Monday, November 03, 2003 9:53 PM Subject: Re: Overheating attributed to Freebsd --sysctl variables notavailable-- > On Mon, 3 Nov 2003 19:57:38 -0500, nw1 <network101@covad.net> wrote: > > > > > > >> What version of FreeBSD are you using? > >> Did you compile amp into the kernel? > > > > I think you're not understanding what I posted @ > > http://69.3.136.141/freebsd/installation/sysctl_variables_missing > > > > The first line has what version I'm running. The entire document @ > > http://69.3.136.141/freebsd/installation/sysctl_variables_missing > > implies; this was a > > running system with no serious issues; meaning; the sysctl items I'm > > speaking of were in > > fact available and working. > > > > If i can figure out how to make these sysctl variables available, I can > > set them like they > > were before, hence my overheating problem is solved. > > > > See what I mean? > > > >> > >> --- nw1 <network101@covad.net> wrote: > >> > The problem can be viewed @: > >> > > >> http://69.3.136.141/freebsd/installation/sysctl_variables_missing > >> > > >> > Basically, the machine is overheating (I believe) > >> > because the cpu's aren't cycling down. > >> > Previously I was able to cycle the processors down > >> > with the following sysctl variables: > >> > > >> > machdep.apm_suspend_delay: > >> > machdep.apm_standby_delay: > >> > > >> > however, for some reason those variables currently, > >> > aren't any where to be found by the > >> > up_and_running system. Please use the hyperlink > >> > above for details. > >> > > >> > Thanks for reading. All feedback is welcome. > > You may want to have a look at /usr/ports/sysutils/fvcool. (If you'd like > a script to run it on startup, Dr. Matthew Seaman posted one to the > mailing list some months ago - January?) > > Jud > _______________________________________________ > freebsd-questions@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-questions > To unsubscribe, send any mail to "freebsd-questions-unsubscribe@freebsd.org" >
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?003e01c3a281$1fdb6a20$0300a8c0>