Trouble with a simple script
 

I am having trouble running a simple script. The purpose of the script is to back one file up into another on a regular basis. For the backup I am using rsync and cron for the repeatability. I'm running Fedora on a virtualbox, if that matters.

The file I'm backing up is /home/username/regfiles.
The file I'm backing up into is /home/username/backup.

The script is:
#!/bin/bash

rsync -av --delete /home/username/regfiles/ /home/username/backup/

This script is located in /home/username/bin/backup.sh

I then used chmod +x to source the script.

I was able run the script from my home directory using ./bin/backup.sh

I tried the cron by making a crontab,
10 * * * * ./bin/backup.sh

I waited until 11 minutes after the hour and used ls backup to check what was in the backup file and it was empty.

Thinking the path wasn't correct I edited the crontab to
15 * * * * /home/username/bin/backup.sh

Again I waited until 16 minutes past the hour and checked the backup file with ls and it was still empty.


I'm not quite sure where I'm going wrong, and any help would be greatly appreciated.

what do the logs say happened?

Restart/Reload the crond service once

As you can see, shebang (i.e. script interpreter) in your script is #!/bin/bash, so can you check which is your shell i.e. login shell of user username?

If shebang and login shell are different, then you will need to run script as:
And crontab entry should be like:

Maybe changing the script to give the full path of rsync would solve it.

cron sets a limited PATH which may not include the directory containing rsync. You could find out what the PATH is when run from cron (and incidentally demonstrate that the script is actually being run by modifying the script to:

when you created the backup script did you have it create a log file? also have you viewed /var/logs/cron to see if it did in fact start?

Thank you for all the suggestions. I tried them all and nothing worked.

I couldn't locate the var/log files or any other logs that would tell me what's going wrong.

I'm stumped!

Which distro? Crontab entries creation is different on different OS, so once mention your OS.

My computer is a windows 7 machine running virtualbox on which I am using Fedora 17.

Once create crontab entries like:
OR

why the quotes around the command? ive set up hundreds of cron jobs over the years and never had to use "" around any of the commands even for custom scripts.

not nit picking, just trying to learn.

@lleb:
It's just a matter of choice, quoting doesn't make any difference.

Thanks for all the suggestions. I figured out what I needed to do.

I made a directory /home/username/cron and put a file named mycron in this directory.

I put my cron table in the mycron file.

then I went to my home directory and used the command crontab ./cron/mycron

When the time came for the backup I checked the backup file and it was written to.

Now I understand cron better. Thanks

Happy to hear this. :)

But what do you think the pb was? How are your crontab entries now look like?

I'm not totally sure what happened, but what I do know is that I can put the cron table in my home directory and I can tell cron where to find it with the crontab command and relative path. I still don't understand why using the crontab -e and absolute path didn't work. Is there a standard location to put scripts? Mine was in my home directory as was my crontab as well as both files involved in the backup. How I figured this out was using the book "Unix Power Tools" by Shelley Powers. On page 494 there is a description that I followed.