The two rsync calls had a delay of 180 seconds between them but when the issue was seen the debug prints from the second rsync call were interspersed with the debug logs of the first rsync call. Our system startup scripts start just one instance of the script which has the two rsync calls. Also when the issue was later detected there was one instance of that script running.
Have you come across errors with bash scripts where they run the command in the background even when not specified to. If so then that seems to be an explanation as to what took place. We did not see any SD card errors or file system errors in general. Regards, Alistair On Sat, Apr 23, 2011 at 9:06 PM, Wayne Davison <[email protected]> wrote: > On Wed, Apr 20, 2011 at 12:44 PM, Alistair Dsouza <[email protected]>wrote: > >> I came across an issue where it seems that the rsync call returned with a >> success but the files that it pulled are not moved immediately to its final >> destination. >> > > I think it more likely that you had 2 instances of the script running at > the same time. You could use something like "shlock" to prevent that from > happening. > > ..wayne.. >
-- Please use reply-all for most replies to avoid omitting the mailing list. To unsubscribe or change options: https://lists.samba.org/mailman/listinfo/rsync Before posting, read: http://www.catb.org/~esr/faqs/smart-questions.html
