BTW, I am not running RsynX at this point, although I tried it and
the results were the same. Cron settings were made with CronniX.
Here is one of the commands from the script:
echo '--lit+music--';
time rsync -e "ssh -i /Users/admin/.ssh/id_dsa" -azvv
--exclude-from=/Users/admin/Desktop/exclude.txt --delete-excluded
email@hidden.6.3:/Volumes/Lit\\\ Music/ /Volumes/LitMusic_Backup
Here is the root user crontab:
0 0 * * 1,2,3,4,5 /usr/bin/open
/Users/admin/Desktop/rsync.command
Well, you have a the open command running a script that calls yet more
commands. Can you just call the script directly without the open
command? Try sticking it in the system crontab and being explicit
about running it as root.
FYI, you can use a range in that last command if you like. 1-5 or
mon-fri, will work as well.
I'd imagine that the open command actually launches Terminal - not a
good idea for an unattended script! To add to what Josh rightly
suggests, you'll want to explicitly define your path to the hfs aware
version of rsync (assuming you're using it; if not, you probably want
to) /usr/local/bin/rsync, both locally, and using the --rsync-path
argument in your script, like this:
FWIW, i use rsync for sync to staging backup servers at a lot of sites,
and there's a massive performance improvement if you run it client
server, instead of over ssh. I set each source server up with xinetd
starting rsync in daemon mode, have my shares set up in
/etc/rsyncd.conf read-only, with access allowed only to the staging
server. On a gig connection with reasonably new servers you can sustain
25-30 MBps.
