Thanks!
This seems to have been the problem. After finding the information cron was
spitting out to the unix mail, it was apparent that the splats (*) used to
short cut the paths so the command would fit into the max length of the command
line where giving problems when run by cron. Don't
We have this Rsync command that does what is desired when ran either directly
OR with a shell script.
/usr/local/bin/rsync -vvv -P --stats -zrtpl --delete
--password-file=/export/home/webuser/.appprod -
-log-file=/exp*/h*/web*/logs/rsync-log --exclude *.htacc*
/exp*/h*/xter*/htdocs/
On Tue, 21 Sep 2010, Ian Skinner wrote:
We have this Rsync command that does what is desired when ran either directly
OR with a shell script.
/usr/local/bin/rsync -vvv -P --stats -zrtpl --delete
--password-file=/export/home/webuser/.appprod --log-file=/exp*/h*/web*/logs/rsync-log
--exclude
On Tue, 2010-09-21 at 15:38 -0700, Ian Skinner wrote:
We have this Rsync command that does what is desired when ran either directly
OR with a shell script.
/usr/local/bin/rsync -vvv -P --stats -zrtpl --delete
--password-file=/export/home/webuser/.appprod -
