03-19-2008
You'd think that the crontab line would be something like this:
[minute] [hour] 1-7,15-24 * 0 [function]
I.E. You're saying run the function at the time specified every Sunday of every month, when the date is 1st thru 7th or 15th thru 24th.
This creates two problems:
A - Because of a quirk in cron, the job will actually run EVERY Sunday AS WELL AS every day from the 1st to the 7th and 15th to the 24th.
B - If that quirk did not exist, you'll miss a week when there are 5 Sundays in the month (this may or may not be a problem for you),
Simple solution:
Have cron run it EVERY Sunday. Then have your script either check the current date, assuming you want to skip the 5th Sunday of the month), or check and set a flag in a file to indicate if it ran that week or not.
Note: This second idea is essentially what Bakunin said.
10 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
Dear all
How can I schedule the cronjob to be run sometime at every first Sunday at every month? I have the edit the cronjob every month now, thanks (2 Replies)
Discussion started by: shanemcmahon
2 Replies
2. UNIX for Dummies Questions & Answers
can someone please check my answers for the crontabs I am making
1. how would I set up a crontab tab executes every 2 minutes each and every day of the week?
answer: 2 * * * * /path/to/file.pl <-- is this correct?
2. how would I set up a crontab that executes every 24 hours at 2am?... (6 Replies)
Discussion started by: Bobafart
6 Replies
3. Shell Programming and Scripting
Hello,
I wanted to run one of my shell script for every sunday at 5PM.
Here is the crontab entry i am using..
00 17 * * 0 /inventory/update.sh > /inventory/update.log 2>&1
The job is not kicking on sunday at the specified time.. Am i missing anthing?
Any help is appreciated... (2 Replies)
Discussion started by: govindts
2 Replies
4. Shell Programming and Scripting
I am using Solaris 9. I wish to run my script every 1 minute inteval. Though i can run it using below entry in crontab.
* * * * /export/home/username/script/file_exist_&_run.sh
in short above script will check whether a specific file exist in a directory. If it found it will inovke another... (10 Replies)
Discussion started by: thepurple
10 Replies
5. Shell Programming and Scripting
Hi,
I would like to trigger a scipt on every Wednesday 12:00PM.
how can schedule this script in CRON command.
Could you please help me on this. (3 Replies)
Discussion started by: koti_rama
3 Replies
6. UNIX for Dummies Questions & Answers
I have two sets of tapes for each week days.
Mon_Set_A ____________Tue_Set_B
Tue_Set_A ____________ Tue_Set_B
Wed_Set_A ___________ Wed_Set_B
Thr_Set_A ____________ Thr_Set_B
Fri_Set_A _____________ Fri_Set_B
I have script that does cold backup of database and then back up to tape.
... (1 Reply)
Discussion started by: Paul.S
1 Replies
7. UNIX for Dummies Questions & Answers
Hi,
I want to run a script starting this 28 Mar 2010 every alternative sunday. Can you give me the crontab entry for the same. Mine is a HP unix. (2 Replies)
Discussion started by: Krrishv
2 Replies
8. UNIX for Advanced & Expert Users
my colleague was asking about this:
is there a way to run a cron job biweekly, like a script five.sh
to run every *OTHER* Friday within November
its part about every other Friday we cant find any documentation.
thx
L (8 Replies)
Discussion started by: lydiaflamp
8 Replies
9. UNIX for Advanced & Expert Users
Hi,
I need to create a autosys job which will run on every sunday at 7:30 AM NY time for each 10 min interval of time.
days_of_week: su
start_mins: 0,10,20,30,40,50
run_window:"07:30"
Is it fine? Please help
Thanks,
Anup (2 Replies)
Discussion started by: anupdas
2 Replies
10. AIX
Hi,
Actually scheduled my test scripts on test severs as shown below. They are supposed to run on 3rd sunday of every month.
Unfortunately it ran on 2nd sunday of the month (suspecting that it will run every sunday). I am sorry if I miss something. Could you please let me know if I did any... (1 Reply)
Discussion started by: System Admin 77
1 Replies
LEARN ABOUT DEBIAN
backintime
backintime(1) USER COMMANDS backintime(1)
NAME
backintime - a simple backup tool for Linux.
This is command line tool. The graphical tools are: backintime-gnome and backintime-kde4.
SYNOPSIS
backintime [ --backup | --backup-job | --snapshots-path | --snapshots-list | --snapshots-list-path | --last-snapshot | --last-snapshot-path
| --help | --version | --license ]
DESCRIPTION
Back In Time is a simple backup tool for Linux. The backup is done by taking snapshots of a specified set of folders.
All you have to do is configure: where to save snapshots, what folders to backup. You can also specify a backup schedule: disabled, every
5 minutes, every 10 minutes, every hour, every day, every week, every month. To configure it use one of the graphical interfaces available
(backintime-gnome or backintime-kde4).
It acts as a 'user mode' backup tool. This means that you can backup/restore only folders you have write access to (actually you can backup
read-only folders, but you can't restore them).
If you want to run it as root you need to use 'su'.
A new snapshot is created only if something changed since the last snapshot (if any).
A snapshot contains all the files from the selected folders (except for exclude patterns). In order to reduce disk space it use hard-links
(if possible) between snapshots for unchanged files. This way a file of 10Mb, unchanged for 10 snapshots, will use only 10Mb on the disk.
When you restore a file 'A', if it already exists on the file system it will be renamed to 'A.backup.currentdate'.
For automatic backup it use 'cron' so there is no need for a daemon, but 'cron' must be running.
user-callback
During backup process the application can call a user callback at different steps. This callback is "$XDG_CONFIG_HOME/backintime/user-
callback" (by default $XDG_CONFIG_HOME is ~/.config).
The first argument is the progile id (1=Main Profile, ...).
The second argument is the progile name.
The third argument is the reason:
1 Backup process begins.
2 Backup process ends.
3 A new snapshot was taken. The extra arguments are snapshot ID and snapshot path.
4 There was an error. The second argument is the error code.
Error codes:
1 The application is not configured.
2 A "take snapshot" process is already running.
3 Can't find snapshots folder (is it on a removable drive ?).
4 A snapshot for "now" already exist.
OPTIONS
-b, --backup
take a snapshot now (if needed)
--backup-job
take a snapshot (if needed) depending on schedule rules (used for cron jobs)
--snapshots-path
display path where is saves the snapshots (if configured)
--snapshots-list
display the list of snapshot IDs (if any)
--snapshots-list-path
display the paths to snapshots (if any)
--last-snapshot
display last snapshot ID (if any)
--last-snapshot-path
display the path to the last snapshot (if any)
-h, --help
display a short help
-v, --version
show version
--license
show license
SEE ALSO
backintime-gnome, backintime-kde4.
Back In Time also has a website: http://backintime.le-web.org
AUTHOR
This manual page was written by BIT Team (<bit-team@lists.launchpad.net>).
version 1.0.10 Mars 2009 backintime(1)