Wayne, thanks for the clarification. We're going to use a SQL query across the SSH tunnel to the database where we are centralizing the errors. Given this structure we can see if the server reported the error such as an interrupt or some dropped connection. If it didn't we'll post the client result. This covers us in there is a drop in the remote link. Anyway, thanks!
Rob "Wayne Davison" <[EMAIL PROTECTED]> wrote in message news:<[EMAIL PROTECTED]>... > On Mon, Sep 18, 2006 at 11:13:04AM -0600, Rob Bosch wrote: > > I've noticed that even if rsync has a non-zero exit code on the client that > > the server still reports an exit status of 0. > > This can happen if the error occurred on the client side because there > is no attempt to get the final exit status from the client side to the > server side. The only thing this server-side exit status tells you is > the exit status of the server process. > > ..wayne.. > -- > To unsubscribe or change options: https://lists.samba.org/mailman/listinfo/rsync > Before posting, read: http://www.catb.org/~esr/faqs/smart-questions.html > -- To unsubscribe or change options: https://lists.samba.org/mailman/listinfo/rsync Before posting, read: http://www.catb.org/~esr/faqs/smart-questions.html
