--===============1347255033==
Content-Type: multipart/signed; micalg=pgp-sha1;
protocol="application/pgp-signature";
boundary="=-LkLpkrdEntI7+QElLIJA"


--=-LkLpkrdEntI7+QElLIJA
Content-Type: text/plain
Content-Transfer-Encoding: quoted-printable

On Tue, 2008-04-08 at 21:27 -0600, Kenneth Seal wrote:
> In my case, rsync displays the error code "rsync error: some files =20
> could not be transferred (code 23)" and it kills my script. Do you =20
> have any advice on how would I go about writing, researching etc. a =20
> script to tell rsync to ignore such errors?


If I were you, I would try to fix the code 23 instead of ignoring it!
Rsync exits with code 23 when at least one non-fatal error occurs that
may affect the correctness of the transfer. Perhaps the errors
currently causing the code 23 are unimportant, but if you ignore code
23, you risk missing more important errors in the future (e.g., the
nonexistence of a source argument).

Look for the specific error messages in the output that are causing the
code 23. If it isn't immediately obvious how to fix them, post them to
the list and I'll take a look. Or if you don't care about copying the
offending files, you can --exclude them.

Matt

--=-LkLpkrdEntI7+QElLIJA
Content-Type: application/pgp-signature; name=signature.asc
Content-Description: This is a digitally signed message part

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.7 (GNU/Linux)

iD8DBQBH/lKpC+xSYN/RlfsRAk39AJ4qRc0YQfHLkvl4hUdgh52sN6A8dgCdGmFe
N0++NR31894Bx9kNaY+WUPY=
=4W4M
-----END PGP SIGNATURE-----

--=-LkLpkrdEntI7+QElLIJA--


--===============1347255033==
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
--===============1347255033==--