Content-Type: multipart/signed; micalg=pgp-sha1;
protocol="application/pgp-signature"; boundary="/Uq4LBwYP4y1W6pO"
Content-Disposition: inline

Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

On Mon, Sep 12, 2005 at 09:36:27AM -0600, Kevin Stussman wrote:
> Thanks for the explanation.
> Since I have no way to know if Oracle has completed the file, I solved
> the problem by making the transfer process smarter and only deleting the
> file once it has been successfully loaded into the secondary. This way
> if the file was corrupted (i.e. sent before completed) then the next
> round of rsync transfers will update the corrupted file with a=20
> completed version (just try try again :-)

Maybe it is possible to user fuser(1) to check if oracle is still sitting
on the file.
> I do have one other question...if rsync does do a checksum after
> the file has been transferred, but the original file has been changed
> during transfer, wouldn't the final checksum then fail? Or does it only
> "snapshot" the original state of the file then compare with the checkum
> the transfer. It would be good if rsync was smart enough to warn/retry
> if the source has changed in transit.

rsync will have a second try if this happens and I think it will warn.

cu, Stefan
Stefan Nehlsen | ParlaNet Administration | sn@parlanet.de | +49 431 988-1260

Content-Type: application/pgp-signature
Content-Disposition: inline

Version: GnuPG v1.2.5 (GNU/Linux)



Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

To unsubscribe or change options: https://lists.samba.org/mailman/listinfo/rsync
Before posting, read: http://www.catb.org/~esr/faqs/smart-questions.html