Submit Hint Search The Forums LinksStatsPollsHeadlinesRSS
14,000 hints and counting!


Click here to return to the 'A shell script to kill the updatedb process' hint
The following comments are owned by whoever posted them. This site is not responsible for what they say.
A shell script to kill the updatedb process
Authored by: olwylee on Sep 22, '03 11:41:27AM

I get the same result as Rob, locate.database is only updated once a week. Mine was last done, (Sep 20 04:32 /var/db/locate.database). My understanding is that updatedb only runs once a week unless you use an app. like OnyX to force the update at other times.

To my knowledge there is no script set up to run 4 times a day by default and if this is happening on your system you might want to investigate as to why and how it got set up that way.



[ Reply to This | # ]
A shell script to kill the updatedb process
Authored by: Scottie on Sep 22, '03 12:58:44PM

My Powerbook hasn't update the locate.database since July 2002. It's never on at 4:30am.

How can you reschedule the scripts for a time when it would be on?



[ Reply to This | # ]
A shell script to kill the updatedb process
Authored by: babertocci on Sep 22, '03 01:41:32PM
The info for when system level periodic scripts will run is contained in /etc/crontab.

30 3 * * 6 root periodic weekly

This is a possible entry for weekly. This means that the weekly script is set to run at 3:30 AM on Saturday. The columns go Minute - Hour - Day of Month - Month - Day of Week - User running the cron job - Command. Any field contain the * is a wildcard. Most of the jobs are set by default to run at the wee hours of the morning. To change them, edit the second column to whatever hour you would rather have them run. You can change weekday and minute as well if you are so inclined.

[ Reply to This | # ]
A shell script to kill the updatedb process
Authored by: langer on Sep 22, '03 10:53:13PM
My Powerbook hasn't update the locate.database since July 2002. It's never on at 4:30am.

How can you reschedule the scripts for a time when it would be on?

Get anacron from fink. Anacron is more suitable than cron for computers that are off much of the time. Instead of running jobs at specific times (such as 4:30 AM on Saturday) it runs them if they haven't been run within a specified interval. For example, you could tell anacron to run updatedb once a week. It can be configured to run the scripts that cron usually runs.

I don't know why anacron isn't set up by default. It can actually be quite important. Until I installed it, my system log files were enormous -- they were never rotated or compressed because cron wanted to do that at 7 AM.

-- Steve

[ Reply to This | # ]

A shell script to kill the updatedb process
Authored by: foobar104 on Sep 23, '03 12:23:53AM

A much better suggestion is to get anacron from <a href="http://www.apple.com/downloads/macosx/unix_open_source/anacron.html">here</a>. That way you don't have to clutter your machine with Fink.



[ Reply to This | # ]
A shell script to kill the updatedb process
Authored by: DC Watts on Sep 24, '03 08:43:32PM


"hasn't updated the locate.database since July 2002."

Scottie, from the KISS standpoint, do you really use locate all that much? 'Cause if you don't, you can easily disable locdb updating and then scream through the weekly crontask in practically no time. Under such circumstances, you might just run the weekly by hand when you need to and avoid editing crontabs. Just depends on how you use your Mac, I guess. Sorry if I've misunderstood.

[ Reply to This | # ]