Date: Wed, 29 Apr 2009 06:18:22 -0700 (PDT) From: Alexander Popov <aopopov@yahoo.com> To: freebsd-questions@freebsd.org, "Daniel C. Dowse" <dcdowse@gmx.net> Subject: Re: atacontrol spindown Message-ID: <24794.51731.qm@web51409.mail.re2.yahoo.com> In-Reply-To: <20090429150722.e9a36808.dcdowse@gmx.net>
next in thread | previous in thread | raw e-mail | index | archive | help
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... Regards, Alexander. --- On Wed, 4/29/09, Daniel C. Dowse <dcdowse@gmx.net> wrote: > From: Daniel C. Dowse <dcdowse@gmx.net> > Subject: Re: atacontrol spindown > To: freebsd-questions@freebsd.org > Date: Wednesday, April 29, 2009, 3:07 PM > On Wed, 29 Apr 2009 05:44:51 -0700 (PDT) > Alexander Popov <aopopov@yahoo.com> wrote: > > > > > Hi, Daniel, > > > > It must be periodic(8), but I have trouble identifying > what exactly could be the trigger. If I look at > /etc/defaults/periodic.conf, it has > > daily_clean_disks_enable="NO". > > With respect to daily checks, I just have the default > setup, nothing that I added myself. > > > > Are there any other configuration options that I > should look at? > > > > Thanks, > > > > Hi, Alexander, > > maybe post the part for the disk in your output of your > daily security > checks here, would be much easier to find out what the > trigger may be. > > What file/directories are accessed, when it comes to that > point? > > IMHO: i believe it is just because the hdd is > "there", so i think when > the cron runs it just checks that the disk is still there. > > > thx > > D.Dowse > > > -- > The only reality is virtual! > _______________________________________________ > 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?24794.51731.qm>