Date: Wed, 29 Apr 2009 14:29:50 +0100 From: Vincent Hoffman <vince@unsane.co.uk> To: aopopov@yahoo.com Cc: freebsd-questions@freebsd.org, "Daniel C. Dowse" <dcdowse@gmx.net> Subject: Re: atacontrol spindown Message-ID: <49F8564E.2070104@unsane.co.uk> In-Reply-To: <24794.51731.qm@web51409.mail.re2.yahoo.com> References: <24794.51731.qm@web51409.mail.re2.yahoo.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On 29/4/09 14:18, Alexander Popov wrote: > Hi, Daniel, > > This is the output: > > Checking setuid files and devices: > > Checking for uids of 0: > root 0 > toor 0 > > Checking for passwordless accounts: > > Checking login.conf permissions: > > ***.home kernel log messages: > +++ /tmp/security.G4QuXmuU 2009-04-29 03:01:08.000000000 +0200 > +ad4: Idle, spin down > +ad4: drive spun down. > +ad8: Idle, spin down > +ad8: drive spun down. > +ad4: request while spun down, starting. > +ad8: request while spun down, starting. > +ad8: Idle, spin down > +ad8: drive spun down. > +ad4: Idle, spin down > +ad4: drive spun down. > +ad4: request while spun down, starting. > > The timestamps in /var/log/messages suggested that "+ad4: request while spun down, starting." happened at 3:01 am. > > It would not be very nice if it was due to cron start up; I don't have any system partitions on those drives, it shouldn't touch them... > Have a look through /etc/defaults/periodic.conf you will see things like daily_status_disks_enable="YES" in there (does a df -l -h on all disks) and I think some of the security ones do checks for new setuid root files, these are all likely to spin up your disks. Vince > Regards, > > Alexander. > >
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?49F8564E.2070104>