Richard Owlett wrote: > On 05/28/2018 07:15 AM, David wrote: >> On 28 May 2018 at 22:07, Richard Owlett <rowl...@cloud85.net> wrote: >> Which would explain why rsync says: >> "rsync: change_dir "/media/root/drescued_commo" failed: No such file >> or directory (2)" >> >> Does that help? >> > > > *DUH* <slaps head and drinks second cup of coffee> > > But that raises another question. > Why does error message identify a protocol problem after having > correctly identified the problem as "No such file or directory". > > Wouldn't "Error 3 -- Errors selecting input/output files, dirs" > be less misleading?
Depends on "what part" was throwing the error -- e.g. if it was ssh or something telling rsync "no can do", then it'd be a different error. -- |_|O|_| Registered Linux user #585947 |_|_|O| Github: https://github.com/dpurgert |O|O|O| PGP: 05CA 9A50 3F2E 1335 4DC5 4AEE 8E11 DDF3 1279 A281
