On Fri, Jun 01, 2001 at 08:44:18AM -0500, Dave Dykstra wrote:
> There is really no way around that problem with rsync. Many other people
> have tried to do similar things and the wisdom on the mailing list has
> always been that rsync via cron is the wrong tool for applications that
> have data that changes frequently and needs to be replicated very soon
> after it changes. You need something more like a distributed database or a
> replicating filesystem, or at the very least call rsync in a synchronous
> manner right after a file has been changed and before the file can change
> again.
Actually, that's not our situation. These files will not be changing -- they
just need to get from the FTP machine over to our application server after
they've been uploaded.
Has anyone tried running rsync under djb's svscan? I'm envisioning a run
script that looks something like this:
#!/bin/sh
PATH=...
find path -type f -mmin +0 -print > file-list
rsync --exclude=/* --include-from=file-list ...
sleep 60
The only problem in this scenario is if the rsync process somehow hangs, then
it would never be restarted and would require manual intervention. Anyone
have suggestions for this?
Thanks to the others who replied.
--Adam
