If your filenames contain two near-identical Unicode characters,
rclone will normalize these, making them identical. This flag
gives you the ability to keep them unique. This might
create unintended side effects, such as duplicating files that
contain certain Unicode characters, when downloading them from
certain cloud providers to a macOS filesystem.
Fixes#4228
This allows rclone to exit with a non-zero return code if no files are
transferred. This is useful when calling rclone as part of a workflow/script
pipeline as it allows the end user to stop processing if no files have been
transferred.
NB: Enabling this option will return in rclone exiting non-zero if there are no
transfers. Depending on how your're currently using rclone in your scripts,
this may break existing setups!
--files-from parses input files by ignoring comments starting with # and ;
and stripping whitespace from start and end of strings.
The --files-from-raw flag was added that reads every line from the file ignoring
comment characters and not stripping whitespace while maintaining
backwards compatibility.
Fixes#3762
This commit adds the `--track-renames-strategy` flag which allows the
user to choose the strategy for tracking renames when using the
`--track-renames` flag.
This can be "hash" or "modtime" or both currently.
This, when used with `--track-renames-strategy modtime` enables
support for tracking renames in encrypted remotes.
Fixes#3696Fixes#2721
This gives you more control over how long rclone will run for, making
it easier to script backups, e.g. via cron. Once the `--max-duration`
time limit is reached, no new transfers will be initiated, but those
already in-flight will be allowed to complete.
Fixes#985
Before this change the expect/continue timeout was set to
--conntimeout which was 60s by default which is too long to wait.
This was noticed when using s3 with a proxy which apparently didn't
support expect / continue properly.
Set --expect-continue-timeout 0 to disable expect/continue.
Before this change --update would transfer any file which was newer
than the destination regardless of whether it had changed or not.
This is needlessly wasteful of bandwidth.
After this change --update will only transfer files if they are newer
**and** they are different (checked with checksum and size).
It's likely a mistake to use `--use-server-modtime` if you're not also using `--update`. It might even make sense to emit a warning in the code when doing this, but for now, I made it more clear in the docs.
I also clarified how `--use-server-modtime` can be useful in the `--update` section.
This was started by Fionera, finished off by Laura with fixes and more
docs from Nick.
Co-authored-by: Fionera <fionera@fionera.de>
Co-authored-by: Nick Craig-Wood <nick@craig-wood.com>
Martin MichlmayrandGitHub
Nick Craig-Wood
Ben ZenkerandNick Craig-Wood
Caleb CaseandNick Craig-Wood
FredandNick Craig-Wood
gitch1andNick Craig-Wood
Tim GallantandNick Craig-Wood
Martin StoneandNick Craig-Wood
Jon FautleyandNick Craig-Wood
Ankur GuptaandGitHub
Bernd SchoolmannandGitHub
Franklyn TackittandNick Craig-Wood
Shing Kit ChanandNick Craig-Wood
Benjapol WorakanandNick Craig-Wood
booshandNick Craig-Wood
Damon PermezelandNick Craig-Wood
Xiaoxing YeandNick Craig-Wood
Thomas EalesandNick Craig-Wood
buengeseandbuengese
Bryce LarsonandNick Craig-Wood
Ivan AndreevandNick Craig-Wood
Cenk AltiandNick Craig-Wood
justinalinandNick Craig-Wood
yparitcherandNick Craig-Wood
Russell DavisandNick Craig-Wood
albertonyandNick Craig-Wood
garry415andNick Craig-Wood
Peter BerbecandNick Craig-Wood
Ben BoeckelandNick Craig-Wood