rsync silently changes special files to regular ones!

2003-08-24 Thread clemens fischer
rsync version 2.5.6 protocol version 26 on FreeBSD 4.8-STABLE i386 "promotes" character special files to regular files: --8<---cut here:--start--->8-- # ll /dev/stdout 8282 crw-rw-rw- 1 root wheel - 22, 1 Aug 23 17:30 /dev/stdout # rsync localhost::rsync/readme /dev/stdout $Id: readme,v 1

Re: Details of local copy

2003-08-24 Thread Clemens Fischer
* 2003-06-20 jw schultz: > It doesn't copy files that don't appear to have changed. > I've used cpio instead of cp myself to take advantage of > such improvements. how did you use cpio? could you please post the command line? clemens -- To unsubscribe or change options: http://lists.samba.o

Re: readdir() and read() errors ignored

2003-08-24 Thread Michael Brown
> > A similar error can occur when open() succeeds but subsequent calls to > > read() fail: under these circumstances rsync will transfer zeroes instead > > of the actual file data and will again report no errors to the user. > > The attached patch fixes both of these problems. > There is a patch

Re: readdir() and read() errors ignored

2003-08-24 Thread jw schultz
On Sun, Aug 24, 2003 at 12:16:47AM +0100, Michael Brown wrote: > We've just been hit rather badly by a very nasty bug that can cause rsync > to silently discard files or fill them with zeroes. It happens when e.g. > opendir() succeeds but readdir() returns an error; rsync does not check > for a