similar to: File over 2GB using Cygwin

I get the following log messages using rsync 2.5.1 compiled on Solaris 8 when using the "hosts allow" option in rsyncd.conf: 2002/01/23 12:09:51 [28276] rsync: reverse name lookup mismatch on fd0 - spoofed address? 2002/01/23 12:10:18 [28276] rsync: connection unexpectedly closed (16 bytes read so far) Resolv.conf/DNS are configured and working properly with both A and PTR records

Does rsync work over an NFS mount? --Karl _________________________________________________________________ Get your FREE download of MSN Explorer at http://explorer.msn.com/intl.asp

To whom it may concern, Would appreciate it if anyone knows how we might easily exclude NFS mount points within a file system from being rsync'd? Regards, Craig Donnelly Andel Consulting 10 Fenchurch Avenue London EC3M 5BN Tel: 0207 6655055 Fax: 0207 6655060

FYI, We've been using the 2.4.7pre1 release for several days now, with nary a hang problem. We haven't seen the EOF bug at all, which was what we upgraded for. This is with transfers of as much as 50GB to set up an initial mirror. The only thing we did was set timeout=0 -- which I guess is unnecessary. The semantics of this flag are a bit unclear. We thought was 'time since

I am having trouble with rsync when I am trying to synchronize a Windows NT volume mounted with smb_fs (FreeBSD) and a unix volume which is also exported with Samba. There are instances where the DOS short name on the NT volume ends up as upper case and then doesn't match filenames which are used in the unix volumes which have been exported by Samba. I don't know if this is a Samba

What is the default block size? I have a few files 30+mb and data is just added to the end of them. It seems like it takes longer to sync them that it was to send it initially. Should I change the block size or something else? I am running: rsync -z -e ssh *.* user@linuxbox:data/ I need to use ssh because I am going over the internet and sending "company data". -------------- next

Hello, Recently while working with rsync as the way to mirror large (several GB) archive on a regular basis, I came across several problems, and also got the ideas about their possible solutions - please could you investigate & consider implementing the features, described below, to future RSYNC releases ? - when the checksumming (consider very large archive, several GB) stage of rsync

I recently installed rsync 2.5.5 on both my rsync server and client being used. I installed the latest version because I was having problems with rsync stalling with version 2.4.6 (I read that 2.5.5 was supposed to clear this up or at least give more appropriate errors). I am still having problems with rsync stalling even after upgrading to 2.5.5. It only stalls in the "/home" tree

Hi. When I discovered rsync, it immediately became one of my most indispensable utilities. It's a real godsend on bandwidth-limited links, especially digital cellular. It works remarkably well in the general case, but I think the algorithm could be improved for one very important special case. Many (or even most) of the updated files I transfer with rsync change only by stuff being appending

Hi, Does rsync lock the source files while its copying? Any input is appreciated. Thank you Dietrich

If I run the following command: # /usr/local/bin/rsync -a --stats -v --delete --force --recursive /source /dest building file list ... done source/file1 source/file2 source/file3 source/file4 source/file5 source/ Number of files: 74 Number of files transferred: 5 Total file size: 1104726340 bytes Total transferred file size: 115163136 bytes Literal data: 463500 bytes Matched data: 114699636

Is anyone else concerned about the fact that rsync doesn't guarantee to produce identical file copies on the the target machine? Don't get me wrong in sounding critical because I think that rsync is a great example of how software should be written. (I often make the observation, as I learn more about Linux, and inevitably find myself comparing open source applications to Microsoft

The problem is caused because rsync does not close its sockets, and WinSock is a quite strict on this. The solution is to shutdown and close the fd. This is a 5-minute hack I've done to fix the obvious occurrences of the problem. It might be better to extend rsyncs cleanup functions for this, but here it is anyway to alert people to the problem and its fix. Max. BEGIN PATCH diff -mru

I just confirmed that data corruption can occasionally occur with rsync 2.5.0 when the -z option is used. My command was the following: rsync -vaz --partial --block-size=65536 --checksum remote:/path/ /localdir The files consisted of a year's worth of email (262MB), broken into one file for each day. At least this doesn't seem to occur silently; I get the message "ERROR: file

Hi I am using rsync for backup on the disks of a Linux backup server. Obviously the server could store more data it the data were compressed. I read the "rsync -> tar" thread. Unfortunately, a compressed file system for Linuthere does not seem to exist yet. However, rsync can use compression for file transfer. Would it be possible to implement an option to store the data on the

Hi, I have some files size 400MB+ that my rsync ends on, error message is : "Write failed: Broken pipe". Without this "big files" everything works smoothe. I searched to find anything about this problem but so far without any luck. Source machine : Solaris 8, rsync-2.4.6 Destination machine : FreeBSD 4.1.1, rsync 2.4.6 Command run(from source machine): rsync

I am getting this error on a Win98SE pc, but not on WinNT4 or Linux Redhat 7.1 or 7.2. Failed to dup/close : The descriptor is a file, not a socket The command I used was rsync -e ssh gas.exe 10.105.50.180:src/ It works like I said on NT4 and from my Linux pc. I have cygwin installed on the win98 and NT. Rsync is version 2.4.6 Is it just because Win9x SU**s? Also where can I get a list of

hi! I have a problem with rsync (current CVS version), running on a win2k machine (rsync compiled using Cygwin). c:\rsync>rsync --version rsync version 2.4.6dev protocol version 24 Copyright (C) 1996-2001 by Andrew Tridgell, Paul Mackerras and others Capabilities: 64-bit files, socketpairs, hard links, symlinks It can DOWNload >2gb files from my linux box (with rsync reporting negative

Andrew and I thought it might be an interesting experiment to move rsync to using BitKeeper rather than CVS for source code control. For a project with rsync's size and activity CVS is actually fine, but it would be a nice "toe in the water" with BitKeeper to get some practical experience before possibly using it on larger projects. BK is moderately well-proven on open source

Hello list, When rsync dir_A to dir_B, I hope I wont make any change to the original dir_B unless the rsync procedure end withour errors, therefore, I hope there's somethig like rsync -av dir_A dir_B_tmp && \ mv dir_B dir_B.bkup && mv dir_B_tmp dir_B This small script can ensure the minimal change time between 2 versions of archive. Is this built in the native rsync