Tim, Thanks for the thought, but I did all that back at the start of September when I first posted all the gory details up.
Rsync, if it worked reliably, would be the perfect tool for the job. ..Trevor.. At 01:03 PM 9/17/2002 -0600, [EMAIL PROTECTED] wrote: >I'm sure your system is fine. What about the rsync, though? If it's >still 2.4.6, you're not getting anywhere. Get the source from >http://rsync.samba.org/ftp/rsync/rsync-2.5.5.tar.gz >untargz it somewhere, and in the directory it creates, which will be named >"rsync-2.5.5", type "./configure ; make ; make install" >On a properly-configured Linux system, those three commands should all run >successfully to completion, leaving you with the rsync binary as >/usr/local/bin/rsync, and the man pages distributed among /usr/local/man. >If your existing version is in /usr/bin or something, and you want to >override it, add "--prefix=/usr" or whatever, to redirect the install. >It's that easy. >If you want to leave off the installation stuff, you can, because the >binary is fully static and relocatable. >I can't guarantee that this will solve your problems. Sometimes, >individual problems can be fixed only by the individual involved. In my >application, I finally had to write a custom app, completely abandoning >rsync, because of the limitations of the platforms I'm required to use. I >still use rsync a lot, but as just another tool, like tar, cp, rsh, >whatever. > >Good luck. > >Tim Conway >[EMAIL PROTECTED] >303.682.4917 office, 303.921.0301 cell >Philips Semiconductor - Longmont TC >1880 Industrial Circle, Suite D >Longmont, CO 80501 >Available via SameTime Connect within Philips, caesupport2 on AIM >"There are some who call me.... Tim?" > > > > >Trevor Marshall <[EMAIL PROTECTED]> >Sent by: [EMAIL PROTECTED] >09/17/2002 11:10 AM > > > To: [EMAIL PROTECTED] > cc: (bcc: Tim Conway/LMT/SC/PHILIPS) > Subject: Re: 'error in rsync protocol data stream' - Tim Conway > Classification: > > > >Tim, >I reported a protocol data stream error on 9/8/2002 >Deatils are in my postes at that time >rsync still fails everytime I run it. > >This time I added three v's as you just suggested and rsync just hung with >two tasks in execution thus: >root 3178 0.1 0.9 1796 868 pts/1 S 09:57 0:00 >/usr/bin/rsync -vvva --delete --exclude=root/snapsh >root 3179 0.0 0.6 1628 632 pts/1 S 09:57 0:00 >/usr/bin/rsync -vvva --delete --exclude=root/snapsh > >and the last data rsync put out was: >make_file(4,var/adm/fillup-templates/i4l.templ) >make_file(4,var/adm/fillup-templates/i4l_b1.templ) >make_file(4,var/adm/fillup-templates/i4l_default.templ) >make_file(4,var/adm/fillup-templates/i4l_hardware.templ) >make_file(4,var/adm/fillup-templates/i4l_hisax.templ) >make_file(4,var/adm/fillup-templates/i4l_icn.templ) >make_file(4,var/adm/fillup-templates/i4l_ignore.templ) >-----------then hangs--------------------- > >Any ideas? >Last time I was told to upgrade my hardware and OS. >I run a solid, scrupulously updated, SuSE 7.3 system on reliable P-II/400 >hardware > >..Trevor Marshall... > >At 10:36 AM 9/17/2002 -0600, you wrote: >>Certainly, you should upgrade your rsync. 2.4.6 had more than its share >>of problems. 2.5.5 is generating few complaints. As far as what's >>actually happening to you, if it continues after the upgrade, give us >>another run with more "v"s. >> >>Tim Conway >>[EMAIL PROTECTED] >>303.682.4917 office, 303.921.0301 cell >>Philips Semiconductor - Longmont TC >>1880 Industrial Circle, Suite D >>Longmont, CO 80501 >>Available via SameTime Connect within Philips, caesupport2 on AIM >>"There are some who call me.... Tim?" >> >> >> >> >>Pascal Bourguignon <[EMAIL PROTECTED]> >>Sent by: [EMAIL PROTECTED] >>09/16/2002 11:39 PM >>Please respond to pjb >> >> >> To: [EMAIL PROTECTED] >> cc: (bcc: Tim Conway/LMT/SC/PHILIPS) >> Subject: 'error in rsync protocol data stream' >> Classification: >> >> >> >>Hello, >> >>While doing a local "rsync" with: >> >> rsync -v -auxHS --force / /backup/ >> >>(on /backup is mounted another disk), I get these errors: >> >>rsync: error writing 4 unbuffered bytes - exiting: Broken pipe >>rsync error: error in rsync protocol data stream (code 12) at io.c(463) >>rsync: error writing 69 unbuffered bytes - exiting: Broken pipe >>rsync error: error in rsync protocol data stream (code 12) at io.c(463) >> >> >>[pascal@thalassa mnt]$ rsync --version >>rsync version 2.5.5 protocol version 26 >>Copyright (C) 1996-2002 by Andrew Tridgell and others >><http://rsync.samba.org/> >>Capabilities: 64-bit files, socketpairs, hard links, symlinks, >batchfiles, >> >> IPv6, 64-bit system inums, 64-bit internal inums >> >> >>What's the problem? >>Should I upgrade rsync? >> >> >>-- >>__Pascal_Bourguignon__ http://www.informatimago.com/ >>---------------------------------------------------------------------- >> The name is Baud,...... James Baud. >>-- >>To unsubscribe or change options: >>http://lists.samba.org/mailman/listinfo/rsync >>Before posting, read: >http://www.tuxedo.org/~esr/faqs/smart-questions.html >> >> >> >>-- >>To unsubscribe or change options: >http://lists.samba.org/mailman/listinfo/rsync >>Before posting, read: >http://www.tuxedo.org/~esr/faqs/smart-questions.html >> >-- >To unsubscribe or change options: >http://lists.samba.org/mailman/listinfo/rsync >Before posting, read: http://www.tuxedo.org/~esr/faqs/smart-questions.html > -- To unsubscribe or change options: http://lists.samba.org/mailman/listinfo/rsync Before posting, read: http://www.tuxedo.org/~esr/faqs/smart-questions.html
