Date: Fri, 13 Nov 2009 15:48:24 -0700 From: David Allen <the.real.david.allen@gmail.com> To: Chuck Swiger <cswiger@mac.com> Cc: freebsd-questions@freebsd.org, James Phillips <anti_spam256@yahoo.ca> Subject: Re: APM Message-ID: <2daa8b4e0911131448h3444444ag67ad05bbbf7df60@mail.gmail.com> In-Reply-To: <E7630082-8284-45A3-AF72-7C3DB2BBB9DA@mac.com> References: <474730.92984.qm@web65506.mail.ac4.yahoo.com> <E7630082-8284-45A3-AF72-7C3DB2BBB9DA@mac.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On 11/13/09, Chuck Swiger <cswiger@mac.com> wrote: > Hi-- > > On Nov 13, 2009, at 12:15 PM, James Phillips wrote: >> I initially set the time-out to 60 seconds, then 300 seconds in a >> vain attempt to see the actual power savings. With a 900 second time- >> out, the drive only spun down once in the past 12 hours. >> >> It appears that syslogd can defer *one* log entry. Understandable, >> since you don't want to loose too many logs in a power failure. > > One of the first things you should consider is either disabling > syslogd entirely, or else setup logging to a RAMdisk (ie, have an > initial copy of what's in /var on the hard disk, setup a RAMdisk and > mount as /var, then copy over the /var tree from hard drive to RAMdisk > during early stages of system boot). There are options available in /etc/defaults/rc.conf to do just that, but how does one copy over the contents of /var at system boot?
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?2daa8b4e0911131448h3444444ag67ad05bbbf7df60>