Hi
On Sun, 05 Mar 2023 07:45:16 -0800 Robin Lee Powell via rsync wrote:
> Oh, yeah, I missed that part. Yeah, don't do that; it's easy to add
> a lock file to a shell script.
Not so easy IMO to do that properly. Use the flock command if your system
provides it.
That said, using a systemd
Oh, yeah, I missed that part. Yeah, don't do that; it's easy to add
a lock file to a shell script.
On Sun, Mar 05, 2023 at 12:30:16PM +0100, Hardy via rsync wrote:
> I second Francis here. You don't need to diagnose incomplete file transfers
> as long as you have racing conditions as you
I second Francis here. You don't need to diagnose incomplete file transfers as
long as you have racing conditions as you described. This leads to strange
result inevitably.
NEVER start several rsync jobs manipulating the same data - especially if there
are modifications to BOTH sides source
I think it's very hard to be sure what's going on with
--remove-source-files ; I think you should drop that option, look
for whether the problem continues, and if you need the files to be
cleaned up, do so in a separate step.
In particular as someone else suggested, are you *sure* the original
Albert Croft via rsync wrote:
> ... I am currently using the 'split' command to break the files
> into 1-GB "chunks" (ex.: foo.tgz.aa, foo.tgz.ab, ...).
> ...
> I am frequently encountering times where the file appears to
> have been transferred but is incomplete. (Example: foo.tgz.ab
> now
Hi.
On Sat, 04 Mar 2023 00:39:52 -0600 Albert Croft via rsync wrote:
> The rsync commands may be launched from command-line or cron, but use
> the same format and options in either case. As a result, there may be
> multiple rsync processes pulling files from the same remote path to the
>
At $work I have an odd situation involving incomplete file transfers,
but I am unsure where the issue may be occurring. Here is the scenario.
Problem:
Sometimes the file transfer seems to have completed, but the file size
does not match that on the remote system.
Details:
I transfer a
