243
edits
Tonyhanson (talk | contribs) No edit summary |
Tonyhanson (talk | contribs) No edit summary |
||
Line 35: | Line 35: | ||
==== cron ==== | ==== cron ==== | ||
cron is a Unix utility that allow you to schedule and run programs (such as backups) on an established schedule. If your Unix system allows you to do so, you could submit an entry that would look like this: | |||
<pre>00 01 * * 0 /some/dir/my_backups </pre> | |||
This would tell the system to run the 'my_backups' program located in the /some/dir directory at 1:00 am every Sunday. The meanings of the five fields are provided below. | |||
<pre>* * * * * | |||
^ ^ ^ ^ ^ | |||
| | | | | | |||
| | | | +----- day of week (0 - 6) (Sunday=0) | |||
| | | +------- month (1 - 12) | |||
| | +--------- day of month (1 - 31) | |||
| +----------- hour (0 - 23) | |||
+------------- min (0 - 59)</pre> | |||
Note that an asterick will be interpreted as every day of week/month/day/hour/minute. You can also have several entries seperated by commas. In the following example my_logs would be run at 1:05 pm every Monday, Wednesday and Friday. | |||
<pre>05 13 * * 1,3,5 /some/dir/my_logs</pre> | |||
If you are lucky your hosting service will provide a GUI interface that makes entering and managing entries a little easier. | |||
==== tar ==== | ==== tar ==== |
edits