You'll have to be more specific if you want some help. The best thing
to do would be to try to create a simple example that you can fully
explain so somebody else could reproduce it. Very often that helps people
to understand the root cause just by going through the exercise. At
the least you'll need to exactly specify the rsync versions, the cygwin
versions, which files weren't copied, and any error messages that are
going to stderr. It doesn't look like you're directing stderr anywhere,
and on most systems that will get sent by email to the owner of the
account that cron is running under. Rather than redirecting job.log
explicitly on every command, you might want to surround the whole thing
with parentheses and add "2>&1", like this:
(
... your commands without the ...
) >> /home/rsync/job.log 2>&1
- Dave Dykstra
On Tue, Jun 25, 2002 at 08:59:14AM -0400, J. Davis
wrote:> Hello,
>
> I have a remote win2k machine and local NT4 machine running rsync over ssh,
by way of cygwin.
> I have a cron script that grabs a directory from remote and puts it on
> local. It' very simple
>
> #!/bin/bash
>
> echo "-------------------------------------" >>
/home/rsync/job.log
> echo "Running rsync job" >> /home/rsync/job.log
> gnudate >> /home/rsync/job.log
> rsync -az --stats -e ssh --exclude "WIN386.SWP" --exclude
"Cache/" --exclude "*.AVB" --exclude "APPS/"
--exclude "virus update/" rsync@x.x.x.x:/cygdrive/e/data
/cygdrive/g/901/>>/home/rsync/job.log
> echo "Done!" >> /home/rsync/job.log
> gnudate >> /home/rsync/job.log
> echo "-------------------------------------" >>
/home/rsync/job.log
>
> It used to always hang but then I removed the -v option after reading
> about that in the archives.
> So according to my job.log the job finishes, however, it's apparent
that
> it has left a great many files on the remote system uncopied. Files that
don't
> match my --exclude args.
> I'm at a loss for how to trouble shoot this one.
>
> -Jake