On 4/29/09, Alexander Popov <aopo...@yahoo.com> wrote:
> Hi, Paul,
> Below is my /etc/crontab. The only thing that is run at 3 am is periodic
If any of scripts from /etc/crontab needs access(just reading, not
considering it is not already cached)
on spindowned hard disk your mission will fail.
If you want to keep logging and logs (via another ways) you could make
memory disk for root
and var slice ... and transfer logs to another media ...
or use another hard disk for that....
> # /etc/crontab - root's crontab for FreeBSD
> # $FreeBSD: src/etc/crontab,v 22.214.171.124 2008/11/25 02:59:29 kensmith Exp $
> #minute hour mday month wday who command
> */5 * * * * root /usr/libexec/atrun
> # Save some entropy so that /dev/random can re-seed on boot.
> */11 * * * * operator /usr/libexec/save-entropy
> # Rotate log files every hour, if necessary.
> 0 * * * * root newsyslog
> # Perform daily/weekly/monthly maintenance.
> 1 3 * * * root periodic daily
> 15 4 * * 6 root periodic weekly
> 30 5 1 * * root periodic monthly
> # Adjust the time zone if the CMOS clock keeps local time, as opposed to
> # UTC time. See adjkerntz(8) for details.
> 1,31 0-5 * * * root adjkerntz -a
> --- On Wed, 4/29/09, Paul B. Mahol <one...@gmail.com> wrote:
>> From: Paul B. Mahol <one...@gmail.com>
>> Subject: Re: atacontrol spindown
>> To: aopo...@yahoo.com
>> Cc: email@example.com, "Daniel C. Dowse" <dcdo...@gmx.net>
>> Date: Wednesday, April 29, 2009, 2:58 PM
>> On 4/29/09, Alexander Popov <aopo...@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?
firstname.lastname@example.org mailing list
To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"