Re: Seeing with comprehension - was [ rsync error -- "Protocol incompatibility" Why?]

2018-05-28 Thread Dan Purgert
Richard Owlett wrote: > Question 1 > [...] > Question 2. > When it ran I happened to be sitting by the display and noticed things > of the form: >> >> var/log/lightdm/x-2.log.old >> 963 100%2.32kB/s0:00:00 (xfr#88022, to-chk=21/128033) >> var/log/speech-dispatcher/ >> var/mail

Re: Seeing with comprehension - was [ rsync error -- "Protocol incompatibility" Why?]

2018-05-28 Thread Richard Owlett
On 05/28/2018 12:57 PM, Dan Purgert wrote: Richard Owlett wrote: Question 1 [...] Question 2. When it ran I happened to be sitting by the display and noticed things of the form: var/log/lightdm/x-2.log.old 963 100%2.32kB/s0:00:00 (xfr#88022, to-chk=21/128033) var/log/speec

Re: Seeing with comprehension - was [ rsync error -- "Protocol incompatibility" Why?]

2018-05-28 Thread Richard Owlett
On 05/28/2018 11:18 AM, Richard Owlett wrote: On 05/28/2018 10:58 AM, Gene Heskett wrote: On Monday 28 May 2018 11:53:26 Richard Owlett wrote: Question 1 I tried to backup another partition. The command I *THOUGHT* I gave was: rsync --verboseĀ  --progress --stats --recursive --times --perms -

Re: Seeing with comprehension - was [ rsync error -- "Protocol incompatibility" Why?]

2018-05-28 Thread Richard Owlett
On 05/28/2018 10:58 AM, Gene Heskett wrote: On Monday 28 May 2018 11:53:26 Richard Owlett wrote: Question 1 I tried to backup another partition. The command I *THOUGHT* I gave was: rsync --verbose --progress --stats --recursive --times --perms --links \ /media/richard/jessie8-6-sda6/ /media/

Re: Seeing with comprehension - was [ rsync error -- "Protocol incompatibility" Why?]

2018-05-28 Thread tomas
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Mon, May 28, 2018 at 10:53:26AM -0500, Richard Owlett wrote: > Question 1 [...] > Is there a graphical editor which would high-lite that "something" is there? Emacs, whitespace mode. It'll show you trailing space, tabs, overlong lines... you name

Re: Seeing with comprehension - was [ rsync error -- "Protocol incompatibility" Why?]

2018-05-28 Thread Gene Heskett
On Monday 28 May 2018 11:53:26 Richard Owlett wrote: > Question 1 > I tried to backup another partition. > > The command I *THOUGHT* I gave was: > > rsync --verbose --progress --stats --recursive --times --perms > > --links \ /media/richard/jessie8-6-sda6/ > > /media/richard/backups/jessie8-6-sd

Seeing with comprehension - was [ rsync error -- "Protocol incompatibility" Why?]

2018-05-28 Thread Richard Owlett
Question 1 I tried to backup another partition. The command I *THOUGHT* I gave was: rsync --verbose --progress --stats --recursive --times --perms --links \ /media/richard/jessie8-6-sda6/ /media/richard/backups/jessie8-6-sda6/ I got a similar error message to last time (i.e. 'file not found'

Re: rsync error -- "Protocol incompatibility" Why?

2018-05-28 Thread The Wanderer
On 2018-05-28 at 09:08, David wrote: > On 28 May 2018 at 22:47, Richard Owlett wrote: > >> 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". > > man rsync says: > "EXIT VALUES >

Re: rsync error -- "Protocol incompatibility" Why?

2018-05-28 Thread Richard Owlett
On 05/28/2018 08:08 AM, David wrote: On 28 May 2018 at 22:47, Richard Owlett wrote: 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". man rsync says: "EXIT VALUES 0 S

Re: rsync error -- "Protocol incompatibility" Why?

2018-05-28 Thread Dan Purgert
Richard Owlett wrote: > On 05/28/2018 07:15 AM, David wrote: >> On 28 May 2018 at 22:07, Richard Owlett 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* > > But that ra

Re: rsync error -- "Protocol incompatibility" Why?

2018-05-28 Thread David
On 28 May 2018 at 22:47, Richard Owlett wrote: > > 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". man rsync says: "EXIT VALUES 0 Success 1 Syntax or usag

Re: rsync error -- "Protocol incompatibility" Why?

2018-05-28 Thread Richard Owlett
On 05/28/2018 07:15 AM, David wrote: On 28 May 2018 at 22:07, Richard Owlett wrote: I had used rsync to back up a different partition with no problems. I used that command as a model to attempt to backup another partition. root@debian-jan13:~# root@debian-jan13:~# rsync --verbose --progress

Re: rsync error -- "Protocol incompatibility" Why?

2018-05-28 Thread Richard Owlett
On 05/28/2018 07:15 AM, likcoras wrote: On 05/28/2018 09:07 PM, Richard Owlett wrote: I had used rsync to back up a different partition with no problems. I used that command as a model to attempt to backup another partition. root@debian-jan13:~# root@debian-jan13:~# rsync --verboseĀ  --progres

Re: rsync error -- "Protocol incompatibility" Why?

2018-05-28 Thread likcoras
On 05/28/2018 09:07 PM, Richard Owlett wrote: > I had used rsync to back up a different partition with no problems. > > I used that command as a model to attempt to backup another partition. > >> root@debian-jan13:~# root@debian-jan13:~# rsync --verboseĀ  --progress >> --stats --recursive --times

Re: rsync error -- "Protocol incompatibility" Why?

2018-05-28 Thread David
On 28 May 2018 at 22:07, Richard Owlett wrote: > I had used rsync to back up a different partition with no problems. > > I used that command as a model to attempt to backup another partition. > >> root@debian-jan13:~# root@debian-jan13:~# rsync --verbose --progress >> --stats --recursive --times

rsync error -- "Protocol incompatibility" Why?

2018-05-28 Thread Richard Owlett
I had used rsync to back up a different partition with no problems. I used that command as a model to attempt to backup another partition. root@debian-jan13:~# root@debian-jan13:~# rsync --verbose --progress --stats --recursive --times --perms --links /media/root/drescued_commo/ /media/root/b

rsync error

2006-07-17 Thread Pupeno
5734 bytes received so far) [sender] rsync error: error in rsync protocol data stream (code 12) at io.c(420) and the command for the backup is (some internal data, like the long list of --excludes, or the username, host and address were remove/replaced): rsync --recursive --relative --link

rsync error

2006-01-24 Thread Pupeno
) adduser.conf 2149 100%0.00kB/s0:00:00 (2, 0.3% of 891) [...snip...] apache-perl/ apache-perl/conf.d/ rsync: writefd_unbuffered failed to write 4 bytes: phase "unknown" [sender]: Broken pipe (32) rsync: close failed on "/mnt/backup/etc/.sudoers.8hvdQc": Permission deni

..doh!, solved, was: ..rsync error (code 12) kills lan mirroring

2004-01-18 Thread Arnt Karlsen
..'zless /usr/share/doc/rsync/sample-rsyncd.conf.gz ' ...and the classic "nogroup". -- ..med vennlig hilsen = with Kind Regards from Arnt... ;-) ...with a number of polar bear hunters in his ancestry... Scenarios always come in sets of three: best case, worst case, and just in case. -- To

..rsync error (code 12) kills lan mirroring

2004-01-17 Thread Arnt Karlsen
arc/,exclude) add_exclude(stable/,exclude) add_exclude(testing/,exclude) add_exclude(unstable/,exclude) add_exclude(source/,exclude) add_exclude(*.orig.tar.gz,exclude) add_exclude(*.diff.gz,exclude) add_exclude(*.dsc,exclude) opening tcp connection to 192.168.2.222 port 873 rsync: read error: Connection

Help for: rsync error: partial transfer (code 23) at main.c(578)

2002-03-26 Thread Thomas K. Burkholder
: Directory not empty rsync: symlink "usr/share/doc/ncurses-term" -> "libncurses5": File exists ... rsync error: partial transfer (code 23) at main.c(578) ... Can anyone explain what code 23 really means (it isn't in the man page) and why the comparatively simple s

rsync:"@ERROR: chroot failed"

2000-01-20 Thread Gerhard Kroder
:$RSYNC_DIR $TO > @ERROR: chroot failed > sh-2.03$ rsync -v -v -v -rltvz $EXCLUDE $RSYNC_HOST::$RSYNC_DIR $TO > @ERROR: chroot failed > sh-2.03$ rsync -v -v -v -v -rltvz $EXCLUDE $RSYNC_HOST::$RSYNC_DIR > $TO > @ERROR: chroot failed > sh-2.03$ any idea