|
|
What benefit?
Except that Apple may or may not step on your modified crontab file in a system update. If you use a StartupItem (and put it in /Library/StartupItems where non-Apple ones belong), you don't have to worry about a system update silently causing your bootup tasks to stop working.
What benefit?
Well, if you add a user crontab and not edit the system crontab (which u shouldnt to anyway) then it will never happen.
What benefit?
Some commands have to be issued by a privileged user, so you couldn't put them in a user crontab. An example of this situation is to have (some) maintenance script run at start-up (like the periodic daily or periodic weekly scripts I pointed at in another comment). Since quite a few computers are off or asleep during the night, most computers have their periodic scripts run at irregular intervals. I'd love to have further extensions to this, something like: @reboot,weekly (which would mean: at reboot, but at most once a week. This would add an administrative burden through). Alternatively: @reboot,monday (at reboot, but on mondays only). Maarten Maarten |
SearchFrom our Sponsor...Latest Mountain Lion HintsWhat's New:HintsNo new hintsComments last 2 daysNo new commentsLinks 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.40 seconds |
|