Any way to test with "dry run" similar to rsync?

Previous Topic Next Topic
 
classic Classic list List threaded Threaded
1 message Options
RL
Reply | Threaded
Open this post in threaded view
|

Any way to test with "dry run" similar to rsync?

RL
Subject says all. Waiting while 100-300+GB move is not optimal, nor is guessing about possible recursion errors which could double that. Is there a way to eliminate file copies but yield the "manifest"?

Would creating an rdiff target with one dummy file and using --compare be a work around? Will that provide file listing? Running a test with --compare initially throws "not an rdiff directory" error. Even if I use --force or --create-full-path.

Thanks for thoughts.
Rufus