hugh at math.byu.edu
Fri Jan 27 11:59:24 MST 2006
I believe you are going about it the right way. You may need to restart
cron to get it to pick up the changes.
On Fri, 27 Jan 2006, Gary Hodges wrote:
> Kubuntu 5.10
> Frequently when I arrive at work in the morning updatedb is chugging
> along. I'd like it to start running earlier so it is not bogging down
> my computer when I want to use it. Best I can tell updatedb is started
> Yesterday I found the following:
> >more /etc/crontab
> # /etc/crontab: system-wide crontab
> # Unlike any other crontab you don't have to run the `crontab'
> # command to install the new version when you edit this file.
> # This file also has a username field, that none of the other crontabs do.
> # m h dom mon dow user command
> 17 * * * * root run-parts --report /etc/cron.hourly
> 25 5 * * * root test -x /usr/sbin/anacron || run-parts --report
> 47 6 * * 7 root test -x /usr/sbin/anacron || run-parts --report
> 52 6 1 * * root test -x /usr/sbin/anacron || run-parts --report
> I changed the hour to 5 from 6 for the cron.daily line, but when I came
> in this morning updatedb is running. In the past updatedb wouldn't run
> for more than about 30 minutes after I arrived so I figured moving its
> start time back an hour would work. Am I going about this the right way?
More information about the LUG