From owner-freebsd-questions Sun Mar 29 22:09:53 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id WAA19689 for freebsd-questions-outgoing; Sun, 29 Mar 1998 22:09:53 -0800 (PST) (envelope-from owner-freebsd-questions@FreeBSD.ORG) Received: from gdi.uoregon.edu (gdi.uoregon.edu [128.223.170.30]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id WAA19678 for ; Sun, 29 Mar 1998 22:09:44 -0800 (PST) (envelope-from dwhite@gdi.uoregon.edu) Received: from localhost (dwhite@localhost) by gdi.uoregon.edu (8.8.7/8.8.8) with SMTP id WAA23635; Sun, 29 Mar 1998 22:09:37 -0800 (PST) (envelope-from dwhite@gdi.uoregon.edu) Date: Sun, 29 Mar 1998 22:09:37 -0800 (PST) From: Doug White Reply-To: Doug White To: George Vagner cc: questions@FreeBSD.ORG Subject: Re: APM support In-Reply-To: <199803231253.GAA01953@mutsgo.dyn.ml.org> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, 23 Mar 1998, George Vagner wrote: > if i enable APM in the boot -c prompt i start getting these > messages when the disks are spun down and there is an access to the drive. > drive wd0 is a Maxtor 85120a6 5.1 GIG wd2 is a WD22100 2.1 GIG Both IDE. > > > Mar 22 23:25:07 mutsgo /kernel: wd0: interrupt timeout: > Mar 22 23:25:07 mutsgo /kernel: wd0: status 58 error 0 > Mar 22 23:40:16 mutsgo /kernel: wd0: interrupt timeout: > Mar 22 23:40:16 mutsgo /kernel: wd0: status 58 error 1 > > I would like to have the disks spin down during periods of inactivity > but hate these messages popping up on the console. > > what can I do? Live with it; they're harmless. FreeBSD doesn't expect the drives to go out to lunch. The IDE controller doesn't signal the host when they're spinning up, assuming a Windoze universe where the system will just block waiting for the disks to come ready. > Another question, How do i properly clear the logs, i read somewhere > that just deleteing them wont do it and can be BAD.. You have to recreate the file then HUP syslogd. Let your machines run over Friday night and the logs will be turned automatically by the cron task that runs /etc/weekly, or on newer systems, newsyslog will roll the logs for you. Doug White | University of Oregon Internet: dwhite@resnet.uoregon.edu | Residence Networking Assistant http://gladstone.uoregon.edu/~dwhite | Computer Science Major To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message