From owner-freebsd-questions@FreeBSD.ORG Wed Apr 29 13:07:24 2009 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id D005A1065674 for ; Wed, 29 Apr 2009 13:07:24 +0000 (UTC) (envelope-from dcdowse@gmx.net) Received: from mail.gmx.net (mail.gmx.net [213.165.64.20]) by mx1.freebsd.org (Postfix) with SMTP id 1A23F8FC22 for ; Wed, 29 Apr 2009 13:07:23 +0000 (UTC) (envelope-from dcdowse@gmx.net) Received: (qmail invoked by alias); 29 Apr 2009 13:07:22 -0000 Received: from p54AA7630.dip.t-dialin.net (EHLO ac1dc0de) [84.170.118.48] by mail.gmx.net (mp027) with SMTP; 29 Apr 2009 15:07:22 +0200 X-Authenticated: #30106961 X-Provags-ID: V01U2FsdGVkX1/6JH9y8cv64G3lfbXXEAneNBcAB0uJXydieZH9Zn f7n0znkWK/QWFi Date: Wed, 29 Apr 2009 15:07:22 +0200 From: "Daniel C. Dowse" To: freebsd-questions@freebsd.org Message-Id: <20090429150722.e9a36808.dcdowse@gmx.net> In-Reply-To: <397932.84499.qm@web51408.mail.re2.yahoo.com> References: <20090429135052.cc870efa.dcdowse@gmx.net> <397932.84499.qm@web51408.mail.re2.yahoo.com> X-Mailer: Sylpheed 2.6.0 (GTK+ 2.12.11; i386-portbld-freebsd7.1) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-Y-GMX-Trusted: 0 X-FuHaFi: 0.63 Subject: Re: atacontrol spindown X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 29 Apr 2009 13:07:25 -0000 On Wed, 29 Apr 2009 05:44:51 -0700 (PDT) Alexander Popov 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!