SCIENTIFIC-LINUX-USERS Archives

August 2005

SCIENTIFIC-LINUX-USERS@LISTSERV.FNAL.GOV

Options: Use Monospaced Font
Show Text Part by Default
Condense Mail Headers

Message: [<< First] [< Prev] [Next >] [Last >>]
Topic: [<< First] [< Prev] [Next >] [Last >>]
Author: [<< First] [< Prev] [Next >] [Last >>]

Print Reply
Sender:
Mailling list for Scientific Linux users worldwide <[log in to unmask]>
Date:
Fri, 19 Aug 2005 06:38:31 +1000
MIME-version:
1.0
Reply-To:
Michael Mansour <[log in to unmask]>
Content-type:
text/plain; charset=iso-8859-1
Subject:
From:
Michael Mansour <[log in to unmask]>
In-Reply-To:
Comments:
To: Harish Narayanan <[log in to unmask]>, Ioannis Vranos <[log in to unmask]> cc: Scientific Linux Users mailing list <[log in to unmask]>
Parts/Attachments:
text/plain (55 lines)
Hi Harish,

> Ioannis Vranos wrote:
> 
> >The "Description" section in the above, mentions that it changes the
DAILY_UPDATE value of 
> >updatedb.conf to "yes", however it is already "yes" in my installation.
Does it mean that 
> >updatedb is already executed once a day in my system? 
> >
> 
> Yes, all you need to do is change that flag to 'yes' to get updatedb 
> to run everyday. If you peek into /etc/cron.daily/slocate.cron, you 
> will see:
> 
> #!/bin/sh
> . /etc/updatedb.conf
> [ "$DAILY_UPDATE" != "yes" ] && exit 0
> renice +19 -p $$ >/dev/null 2>&
> 
> Which checks the flag and runs updatedb "daily" accordingly. Since 
> yours is already 'yes', it will run "daily".
> 
> >If yes, when exactly?
> >  
> >
> To figure out what that really means, you peek into /etc/crontab to see:
> 
> <snip>
> 
> # run-parts
> 01 * * * * root run-parts /etc/cron.hourly
> 02 4 * * * root run-parts /etc/cron.daily
> 22 4 * * 0 root run-parts /etc/cron.weekly
> 42 4 1 * * root run-parts /etc/cron.monthly
> 
> So there you have it. It runs updatedb (or tries to) at 4:02 AM, 
> from the second line. You can change these to more convenient times, 
> like when the computer is actually on (and when you're not sitting 
> at it). On a related note, I tried asking about something similar[1] 
> -- I wanted to move this over to an equivalent "anacrontab" -- but 
> didn't know how. If someone has any ideas, I'd appreciate the help.
> 
> Harish
> 
> [1] Question 3 on 
> http://listserv.fnal.gov/scripts/wa.exe?A2=ind0508&L=scientific-
> linux-users&T=0&F=&S=&P=13080

I don't really use anacron as I've only ever dealt with 24x7 systems, so never
needed to. However, wouldn't it be as easy as moving the slocate cron out of
the cron.daily directory to another drop file directory?

Michael.

ATOM RSS1 RSS2