similar to: how to prevent forward/reverse lookups

Hi. My goal is to use rsync to syncronize box1 and box2. On box2, I have a tapedrive which I write the data I syncronize from box1 every night. On box1, my /etc/rsyncd.conf looks like this: root@box1# cat /etc/rsyncd.conf max connections = 1 syslog facility = local6 [tmp] path = /tmp read only = yes comment = export of /tmp hosts allow = box2 auth users

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

I have so far been unable to get rsync to work properly in a test setup. Does anyone have any ideas? Both PCs are running RedHat 7.2. The Server: IP Address 192.168.0.202 Server Name: RH72TB hosts.allow ALL: 192.168.0.201 rsyncd.conf: [testmodule] path = /tmp The Client: IP Address 192.168.0.201 hosts file: 192.168.0.202 RH72TB I have run "rsync --daemon" on the server.

I have a similar problem with rsync, though it's not consistent. sometimes, things just don't come over, and sometimes, things just don't get deleted. Repeated runs usually correct it. If it's the case of a directory being replaced with a non-directory, you'll have to add "--force" to get it to happen. Hope it helps. Tim Conway tim.conway@philips.com

Hi! I am doing backups from a number of machines to an rsync server. For some time I was trying to come up with a solution, which would prevent users from peeking at each other's files, which are backed up. Finally, I've hacked rsync, introducing a new option "write only" for rsyncd.conf. When set to true, this option forbids the transfers from server to the client, thus solving

Any time I try and setup a hosts allow option in the modules I get the following errors: I'm running this from the client. rsync -rv ws2743::test3 /pw/prog/BOS/stuff @ERROR: access denied to test3 from unknown (::3) rsync: connection unexpectedly closed (62 bytes read so far) rsync error: error in rsync protocol data stream (code 12) at io.c(139) I get the following from the log file on the

Hello, I think i may have found a bug in the "max clients" option in rsyncd.conf [we use rsync-2.5.5; All platforms I tried (Irix-6.5.14 and various linux flavours) show the behaviour explained below] The manpage says: |max connections | The "max connections" option allows you to specify | the maximum number of simultaneous connections you | will allow to

I have some rsync defined as a server on one of my production systems and use to to sync out various configuration files for services running on the box (dhcpd, dns named.conf files & the like). Both ends are Compaq Alpha/Tru64 5.1 systems running rsync 2.5.5. I'm having a fit trying to include certain files in specific subdirectories under the main path; one such example is below:

Before I start let me say I'm a relative newbie to rsync so bear with me. I've just installed version 2.5.5 and set up the following files on the server: inetd.conf rsync stream tcp nowait root /usr/local/bin/rsync rsyncd --daemon rsync.conf [www] path = /test/test2 comment = Test services rsync 873/tcp then I run 'rsync --daemon'

Is it true that when running rsync via ssh (i.e. rsync -e ssh ...) the rsyncd.conf file is not applicable on the remote since rsync is launched via the ssh exec call once connected rather than from rsyncd as in a direct connect. If so, I am trying to find the best way to restrict rsync -e ssh on the remote machine. Prepending the authorized_keys entry with command='rsync ...' 1024...

Howdy, I'm trying to get a report from rsync using the -n option which will produce a report of files that are different in a ls -al kind of style so one could analyze what's different before possibly clobering a good file. Is this possibly in the works or does anyone have any ideas on how this might be done. It seems like a useful option to rsync to have. Regards, George...

Rsync reports the status code of the remote command. So in some situations the status code is successful when the command fails. Rsync of a remote file to a local read-only directory fails, but exits with $status = 0. I'd like to get $status = 23. Is it possible? Local copy fails with status = 23 > mkdir /tmp/nowrite > chmod -w /tmp/nowrite > rsync /etc/group /tmp/nowrite || echo

I am copying from a rsync --daemon (have tried from both W2K/cygwin & Linux daemons) to a W2K machine. Some files get copied every time even though they haven't been touched since the last copy. I have experimented and deturmined that the file size seems to be important. If the file is between 926 & 933 bytes long it will always be copied!! Other sizes and possibly other aspects of

I just took a look at the 2.5.5 codebase to see how easy it would be to write a little driver script that downloads a big directory tree from an rsync daemon the chunky way (get a list of a module's subdirectories and do the transfer by subdirectory). The reason for doing this is obvious when you have large directory trees, as is the case for many of us. Unfortunately the way list_only is

Hi, We got the following error messages when we ran rsync 2.5.2 from Solaris-5.5.1 to Solaris-5.8. vl121909/jagcdms_ch+_diags/sys/sys_l/ch_sys/rtl/systop.v vl121909/jagcdms_ch+_diags/sys/sys_l/ch_sys/rtl/sysup_esat.v vl121909/jagcdms_ch+_diags/sys/sys_l/ch_sys/rtl/upesat_defines.h wrote 63878001383 bytes read 1529124 bytes 1246928.64 bytes/sec total size is 148182624008 speedup is 2.32 rsync

Hello, I am noticing inconsistencies when using a trailing slash on the source directories in conjunction with the '--delete' option. In one instance when using a trailing slash files get deleted from subdirectories in the destination tree. In the other instance they don't. I am using rsync 2.5.5. The following are the scenarios: Scenario 1 ---------- *nix(src) ---> *nix(dest)

I am trying to finalize the use of rsync for updatiung a new nfs server before we take the old one offline. I keep getting the following warning during the rsync process: Warning: unexpected rad size of 0 in map_ptr Any ideas where this comes from and how to make it go away? I am using rsync 2.5.2 on Solaris 8 to pull data from rsync 2.5.2 on Solaris 7. Bob roconnor@vectorpartners.com

Hi there, we have an odd problem, which maybe how rsync is intended to work, but I think not: On server side, we run rsync in daemon mode with a share [foo] that has a serverside path of /foo. On client side, we invoke rsync -zavuSH --delete server::foo/ /foo. The rsync daemon uses an exclusion list. The problem is, the client rsync deletes clientside whatever is in the exclusionlist. If I read

Maybe this is a ssh problem - but are you aware of the general issue ? http://bugzilla.mindrot.org/show_bug.cgi?id=182 Summary: ssh should still force SIGCHLD to be SIG_DFL when calling ssh-rand-helper Product: Portable OpenSSH Version: 3.1p1 Platform: ix86 OS/Version: All Status: NEW Severity: normal

I came up with a patch to fix the problem of IO Errors caused by excluded files as did Eugene V. Chupriyanov below. Is there a chance that this change will show up in a future version of rsync? Is there a reason that we should not ignore IO errors when copy_links is off? Just want to make sure that I'm not missing something here that may corrupt my syncs.... Here's the version that