rsync does not copy hidden directories
We are using rsync and have noticed that it fails to copy hidden directories. I looked through the doc and it doesn't look like there's a flag to get rsync to not skip hidden (dot) directories. Am I missing something or is this By Design? If By Design, I think it should be changed. Michelene Chon Manager, SCM (Software Configuration Management) GetThere, a Sabre company [EMAIL PROTECTED] Phone: (650) 752-1794 Cell: (650) 208-4172
Re: unexpected EOF in read_timeout
Michelle/Tim, I ocassionally get this message under 2.4.7pre1 -- I just call it a network error and ignore it, but perhaps there is still a rsync protocol problem. TCP is pretty good about retry/resend under bad network conditions. Network hiccups shouldn't really be hitting us this often or severe, right? Is the receiving side giving up or hanging up too soon? One good thing about this error -- at least it isn't hanging forever like 2.4.6 would often do. my errors look like this: rsync: connection to server unexpectedly closed (69872 bytes read so far) rsync error: error in rsync protocol data stream (code 12) at io.c(255) eric willem wrote: > > [EMAIL PROTECTED] wrote: > > > Michelle: I get the same sort of results. Solaris 7, rsync 2.4.6, with the nohang >patches, or with 2.4.7pre1. If you trace the execution, you'll probably find i/o >errors. I can't find out what they are, and would expect the kernel to take care of >any > > disk or network errors, leaving me wondering what rsync is choking on. We've got >all the latest patches to Solaris, so i'm pretty sure it's not a case of rsync >overstressing the tcp implementation, especially as i bwlimit the transfer to >1000kbps. > > I've got 2328543 objects (files, directories, symlinks) in 116473553K, on NAS at >each end, reached by NFS. I have to break my jobs up into smaller chunks, which >makes it hard to have it delete things. > > Anybody else have any ideas? > > > > Tim Conway > > [EMAIL PROTECTED] > > 303.682.4917 > > Philips Semiconductor - Longmont TC > > 1880 Industrial Circle, Suite D > > Longmont, CO 80501 > > Available via SameTime Connect within Philips > > Available as n9hmg on AIM > > perl -e 'print pack(, >19061,29556,8289,28271,29800,25970,8304,25970,27680,26721,25451,25970), ".\n" ' > > "There are some who call me Tim?" > > > > Michelle Brownsworth <[EMAIL PROTECTED]>@lists.samba.org on 09/10/2001 06:34:16 PM > > > > Sent by: [EMAIL PROTECTED] > > > > To: [EMAIL PROTECTED] > > cc: (bcc: Tim Conway/LMT/SC/PHILIPS) > > Subject: RE: unexpected EOF in read_timeout > > Classification: > > > > Sadly, I don't seem to be having any better luck with 2.4.7pre1: > > > > su-2.05# ./rsync_nova.sh > > receiving file list ... done > > wrote 16 bytes read 6620 bytes 13272.00 bytes/sec > > total size is 1309032 speedup is 197.26 > > receiving file list ... done > > wrote 16 bytes read 4458 bytes 2982.67 bytes/sec > > total size is 6037628 speedup is 1349.49 > > receiving file list ... done > > wrote 16 bytes read 450 bytes 932.00 bytes/sec > > total size is 34693 speedup is 74.45 > > receiving file list ... done > > mysql/kendall/car.MYD > > Connection to nova closed by remote host. > > rsync: connection to server unexpectedly closed (26372 bytes read so far) > > rsync error: received SIGUSR1 or SIGINT (code 20) at rsync.c(229) > > rsync error: received SIGUSR1 or SIGINT (code 20) at main.c(693) > > > > .\\ichelle > > - > > Michelle Brownsworth > > System Administrator > > PrimeLogic Communications > > http://www.primelogic.com > > sorry to get your hops up but I've no Ideas > but I'm wondering how you limit your band width use uther solaris > I wan't to do that for an ftp connection. can you help me with that? -- __ Eric T. Whiting AMI Semiconductors
Re: unexpected EOF in read_timeout
[EMAIL PROTECTED] wrote: > Michelle: I get the same sort of results. Solaris 7, rsync 2.4.6, with the nohang >patches, or with 2.4.7pre1. If you trace the execution, you'll probably find i/o >errors. I can't find out what they are, and would expect the kernel to take care of >any > disk or network errors, leaving me wondering what rsync is choking on. We've got >all the latest patches to Solaris, so i'm pretty sure it's not a case of rsync >overstressing the tcp implementation, especially as i bwlimit the transfer to >1000kbps. > I've got 2328543 objects (files, directories, symlinks) in 116473553K, on NAS at >each end, reached by NFS. I have to break my jobs up into smaller chunks, which >makes it hard to have it delete things. > Anybody else have any ideas? > > Tim Conway > [EMAIL PROTECTED] > 303.682.4917 > Philips Semiconductor - Longmont TC > 1880 Industrial Circle, Suite D > Longmont, CO 80501 > Available via SameTime Connect within Philips > Available as n9hmg on AIM > perl -e 'print pack(, >19061,29556,8289,28271,29800,25970,8304,25970,27680,26721,25451,25970), ".\n" ' > "There are some who call me Tim?" > > Michelle Brownsworth <[EMAIL PROTECTED]>@lists.samba.org on 09/10/2001 06:34:16 PM > > Sent by: [EMAIL PROTECTED] > > To: [EMAIL PROTECTED] > cc: (bcc: Tim Conway/LMT/SC/PHILIPS) > Subject: RE: unexpected EOF in read_timeout > Classification: > > Sadly, I don't seem to be having any better luck with 2.4.7pre1: > > su-2.05# ./rsync_nova.sh > receiving file list ... done > wrote 16 bytes read 6620 bytes 13272.00 bytes/sec > total size is 1309032 speedup is 197.26 > receiving file list ... done > wrote 16 bytes read 4458 bytes 2982.67 bytes/sec > total size is 6037628 speedup is 1349.49 > receiving file list ... done > wrote 16 bytes read 450 bytes 932.00 bytes/sec > total size is 34693 speedup is 74.45 > receiving file list ... done > mysql/kendall/car.MYD > Connection to nova closed by remote host. > rsync: connection to server unexpectedly closed (26372 bytes read so far) > rsync error: received SIGUSR1 or SIGINT (code 20) at rsync.c(229) > rsync error: received SIGUSR1 or SIGINT (code 20) at main.c(693) > > .\\ichelle > - > Michelle Brownsworth > System Administrator > PrimeLogic Communications > http://www.primelogic.com sorry to get your hops up but I've no Ideas but I'm wondering how you limit your band width use uther solaris I wan't to do that for an ftp connection. can you help me with that?
RE: unexpected EOF in read_timeout
Michelle: I get the same sort of results. Solaris 7, rsync 2.4.6, with the nohang patches, or with 2.4.7pre1. If you trace the execution, you'll probably find i/o errors. I can't find out what they are, and would expect the kernel to take care of any disk or network errors, leaving me wondering what rsync is choking on. We've got all the latest patches to Solaris, so i'm pretty sure it's not a case of rsync overstressing the tcp implementation, especially as i bwlimit the transfer to 1000kbps. I've got 2328543 objects (files, directories, symlinks) in 116473553K, on NAS at each end, reached by NFS. I have to break my jobs up into smaller chunks, which makes it hard to have it delete things. Anybody else have any ideas? Tim Conway [EMAIL PROTECTED] 303.682.4917 Philips Semiconductor - Longmont TC 1880 Industrial Circle, Suite D Longmont, CO 80501 Available via SameTime Connect within Philips Available as n9hmg on AIM perl -e 'print pack(, 19061,29556,8289,28271,29800,25970,8304,25970,27680,26721,25451,25970), ".\n" ' "There are some who call me Tim?" Michelle Brownsworth <[EMAIL PROTECTED]>@lists.samba.org on 09/10/2001 06:34:16 PM Sent by: [EMAIL PROTECTED] To: [EMAIL PROTECTED] cc: (bcc: Tim Conway/LMT/SC/PHILIPS) Subject: RE: unexpected EOF in read_timeout Classification: Sadly, I don't seem to be having any better luck with 2.4.7pre1: su-2.05# ./rsync_nova.sh receiving file list ... done wrote 16 bytes read 6620 bytes 13272.00 bytes/sec total size is 1309032 speedup is 197.26 receiving file list ... done wrote 16 bytes read 4458 bytes 2982.67 bytes/sec total size is 6037628 speedup is 1349.49 receiving file list ... done wrote 16 bytes read 450 bytes 932.00 bytes/sec total size is 34693 speedup is 74.45 receiving file list ... done mysql/kendall/car.MYD Connection to nova closed by remote host. rsync: connection to server unexpectedly closed (26372 bytes read so far) rsync error: received SIGUSR1 or SIGINT (code 20) at rsync.c(229) rsync error: received SIGUSR1 or SIGINT (code 20) at main.c(693) .\\ichelle - Michelle Brownsworth System Administrator PrimeLogic Communications http://www.primelogic.com
Q: when is the next release planned?
Hi everybody! Could you please tell me when the next release is planned? I ask this because I saw in CVS that rsync+ is merged but not released, which I'd need. If it is probable less than 2 weeks I'll wait - if it's certainly more than 3 I'll get the CVS sources and start working with them. Thanks for all answers! Regards, Phil
rsync hangs after a number of files
hi, I'm using rsync to backup our company storage system but wen I execut rsync to start copying it copy's only a certan number of files and dirs 257 this id the line I execute I have setup ssh and rsync so that it won't bodder me for a password. this is the line I use to start rsync rsync -vcrulog -e ssh --delete --password-file=/etc/rsyncpasswd \ /exports/set0/ [EMAIL PROTECTED]:/exports/set5/ thx for all you reactions greatings willem
Re: Buglet in rsync-2.4.7pre1
On 10 Sep 2001, Marc Espie <[EMAIL PROTECTED]> wrote: > The popt dir was forgotten from the configure script, so it is not created > for builds in a separate directory. > > e.g., change > AC_OUTPUT(Makefile lib/dummy zlib/dummy) > into > AC_OUTPUT(Makefile lib/dummy zlib/dummy popt/dummy) > > reconfigure, rebuild. Thanks! Committed. -- Martin
Re: Running rsync on machines in different timezones
On 10 Sep 2001, Ragnar Kj?rstad <[EMAIL PROTECTED]> wrote: > [ I'm not on the list - please CC replies to me ] > > Does rsync work properly (is it able to determine wich files are new > correctly) when ran on machines set up with different timezone-settings? Yes. rsync works in unix timestamps, which are in universal time. You should try to have the machines' clocks synchronized, but it is not really necessary. -- Martin
