Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.debian.user > #196155
| From | Dan Purgert <dan@djph.net> |
|---|---|
| Newsgroups | linux.debian.user |
| Subject | Re: rsync error -- "Protocol incompatibility" Why? |
| Date | 2018-05-28 15:30 +0200 |
| Message-ID | <vUqnL-80P-3@gated-at.bofh.it> (permalink) |
| References | <vUp8n-7mU-19@gated-at.bofh.it> <vUpi2-7pV-13@gated-at.bofh.it> <vUpL3-7zb-7@gated-at.bofh.it> |
| Organization | A noiseless patient Spider |
Richard Owlett wrote: > On 05/28/2018 07:15 AM, David wrote: >> On 28 May 2018 at 22:07, Richard Owlett <rowlett@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
Back to linux.debian.user | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread
rsync error -- "Protocol incompatibility" Why? Richard Owlett <rowlett@cloud85.net> - 2018-05-28 14:10 +0200
Re: rsync error -- "Protocol incompatibility" Why? likcoras <likcoras@riseup.net> - 2018-05-28 14:20 +0200
Re: rsync error -- "Protocol incompatibility" Why? Richard Owlett <rowlett@cloud85.net> - 2018-05-28 14:40 +0200
Re: rsync error -- "Protocol incompatibility" Why? David <bouncingcats@gmail.com> - 2018-05-28 14:20 +0200
Re: rsync error -- "Protocol incompatibility" Why? Richard Owlett <rowlett@cloud85.net> - 2018-05-28 14:50 +0200
Re: rsync error -- "Protocol incompatibility" Why? David <bouncingcats@gmail.com> - 2018-05-28 15:10 +0200
Re: rsync error -- "Protocol incompatibility" Why? Richard Owlett <rowlett@cloud85.net> - 2018-05-28 15:40 +0200
Re: rsync error -- "Protocol incompatibility" Why? The Wanderer <wanderer@fastmail.fm> - 2018-05-28 16:10 +0200
Re: rsync error -- "Protocol incompatibility" Why? Dan Purgert <dan@djph.net> - 2018-05-28 15:30 +0200
Seeing with comprehension - was [ rsync error -- "Protocol incompatibility" Why?] Richard Owlett <rowlett@cloud85.net> - 2018-05-28 18:00 +0200
Re: Seeing with comprehension - was [ rsync error -- "Protocol incompatibility" Why?] Gene Heskett <gheskett@shentel.net> - 2018-05-28 18:00 +0200
Re: Seeing with comprehension - was [ rsync error -- "Protocol incompatibility" Why?] Richard Owlett <rowlett@cloud85.net> - 2018-05-28 18:20 +0200
Re: Seeing with comprehension - was [ rsync error -- "Protocol incompatibility" Why?] Richard Owlett <rowlett@cloud85.net> - 2018-05-28 18:30 +0200
Re: Seeing with comprehension - was [ rsync error -- "Protocol incompatibility" Why?] <tomas@tuxteam.de> - 2018-05-28 18:10 +0200
Re: Seeing with comprehension - was [ rsync error -- "Protocol incompatibility" Why?] Dan Purgert <dan@djph.net> - 2018-05-28 20:10 +0200
Re: Seeing with comprehension - was [ rsync error -- "Protocol incompatibility" Why?] Richard Owlett <rowlett@cloud85.net> - 2018-05-28 21:10 +0200
csiph-web