|
|
For Server . . .
If you use OS X server you can actually do this in a different way, that is slightly better.
Allows you to put in multiple scripts starting with a number to prioritize them.
As an example on my server systems I put this same script in the following location:
So that it runs weekly, and is the last script run.
The periodic folder appears in OS X Client, but when I tried using it the scripts there never ran.
For Server . . .
Periodic works fine on OS X client as well - there must have been another problem.
For Client . . .
in OS X client the default system crontab does not use the weekly folder; it uses an alias named weekly which points to the default weekly job contained in the folder. to use the weekly folder you have to edit the crontab.
For Client . . .
You sure you have to edit the crontab?
my 'system' crontab for root is empty but /etc/crontab contains
The /etc/weekly symlink does indeed point to periodic/weekly/500.weekly, but it doesn't seem to have any effect on the periodic program.
Just put a script in the appropriate directory, make it executable and check your script return code (it is important). As always RTFM; in this case, man periodoc. |
SearchFrom our Sponsor...Latest Mountain Lion HintsWhat's New:HintsNo new hintsComments last 2 daysLinks last 2 weeksNo recent new linksWhat's New in the Forums?
Hints by TopicNews from Macworld
From Our Sponsors |
|
Copyright © 2014 IDG Consumer & SMB (Privacy Policy) Contact Us All trademarks and copyrights on this page are owned by their respective owners. |
Visit other IDG sites: |
|
|
|
Created this page in 0.13 seconds |
|