similar to: Rsync from NT to UNIX

Ah... there's your answer. ssh is working fine, as you say, but you're invoking rsync without telling it to user ssh, so it's using rsh. If you've got this, you don't need rsyncd.conf. The syntax you're using tells rsync to use an external transport. rsync -e ssh file rmt_host:/tmp Tim Conway tim.conway@philips.com 303.682.4917 Philips Semiconductor - Longmont TC 1880

Sonu: I'm giving the whole history to the rsync list. If the tests i subscribed passed, yet you get that error, it's more in depth than i can go into. You've got 1 hour, let's hope somebody immediately recognizes the problem. I've got some ideas, but no time to explore any more for you. Gentlemen: does anybody see a quick resolution for Sonu? Looks like he's

I keep getting these smarmy sermons from somebody's mail account. I include my response to it below, though from its message, it probably won't be read. Tim Conway tim.conway@philips.com 303.682.4917 Philips Semiconductor - Longmont TC 1880 Industrial Circle, Suite D Longmont, CO 80501 Available via SameTime Connect within Philips, n9hmg on AIM perl -e 'print pack(nnnnnnnnnnnn,

Your users have rsh access to the machine, and are getting wherever they want, using the server:/path syntax. if they were using the server::module syntax, they would be restricted to only what's provided by the modules. If you don't want them getting everything all over the system, you will need to prevent shell access. Tim Conway conway.tim@sphlihp.com reorder name and reverse

I see very odd results from rsync 2.4.7pre1, the latest cvs version (sept 12, i think was the last modified file). We have a number of network-attached storage devices. 10/100 ethernet, nfs2 mounted (under nfs3, they buffer deletes, and recursive deletions fail). Usually, these are kept syncronized across a wan by a nightly cronjob, We have a few we keep in reserve, which we syncronize

the --pasword-file= option is only for passing a password to a rsync server, as you have set up with the rsync --daemon process. Your rsyncd.conf file is fine, too. The problem is that you aren't calling your rsync daemon from your commandline. You are trying to connect via rsync to host as axlink and start a 'rsync --sender' process, to transfer data within the ssh process.

Hi, I am trying to mirror a server every night using rsync. I have to backup multiple directories and multiple individual files. I also want to use ssh as transport. The problem is that I cannot get ssh to work without asking password for each step. I tried the public key thing but it doesnt work. Can some one give instructions for a layman like me. Also I want to know how to pass argument to

checking whether the C compiler (/usr/local/bin/gcc -O -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 ) works... no configure: error: installation or configuration problem: C compiler cannot create executables. Any solution of this ? Please. regards. -------------- next part -------------- HTML attachment scrubbed and removed

When rsync starts I get the following messages in my log file Jan 11 11:00:04 WEB1 rsyncd[31281]: rsync: bind failed on port 873 Jan 11 11:00:04 WEB1 rsyncd[31281]: rsync error: error in socket IO (code 10) at socket.c(361) Anybody know what might be causing this? David

Hi All, We have clients which dynamic IPs which we have setup with <host>.dyndns.org addresses. We have added these to the rsync.conf 'hosts allow=" but they are being denied access.. Is there anyway around this? Matt

I'm not sure what the problem is. Here's a snip of my log (very similar setup, but from server to remotes): 2001/05/17 14:26:59 [29226] rsync on ToolSyncModules/ToolSyncModuleList from irvnetsvr (134.27.9.31) 2001/05/17 14:27:00 [29226] wrote 23292 bytes read 128 bytes total size 23179 2001/05/17 14:27:01 [29227] rsync on ToolSyncModules/ToolSyncMastersList from irvnetsvr

This is my first post so first of all I will say hello to everyone. I have rsync configured and working properly on my local network however when I try to connect from a remote host (one located in a different state) the connection times out. I was wondering if there was another way to set the timeout besides in the rsyncd.conf file? As I said the connection works fine on the internal lan, but

Hi all, I have started the rsync in deamon mode. When I use the following command: rsync --port 9876 u018::treeA it seems to work fine but no files are copied from the server. Using rsync without the deamon works fine. I tried to debug it a little bit, but I am unable to figure out what's wrong. 337:david@u050 /export/treeA> rsync -r -vvv --port 9876 u018::treeA opening tcp

This is where it sets a sort of 60 second timeout if you don't set a timeout at all. As far as what it affects, I'm not that good with the code. I just know that my big syncs would die in almost exactly 1 minute unless I specified a timeout, and then would die at that timeout until i got it very large. +++++++++++++++++++++++++++++++++++++++++++++++++++++ Tools@willy

Hi, I have a rsync server set up. Can i push data from the server to another machine instead of pulling data from that machine. when i try to do that i get this error. mkdir tohost:/tmp ; No such file or directory. But the directory exists. This is the command i executed. rsync -avz --rsync-path=/usr/bin/rsync fromhost::test tohost:/tmp This works fine if iam logged onto "tohost"

Are there issues between different versions of rsync? Specifically I have a 2.4.6 on solaris 8 pushing to a 2.3.0 on solaris 2.6 over ssh(F-Secure version). The issue that I am seeing is that when I use the following command: rsync --delete -rlvp -e ssh2 $localdir user@host:remotedir The user and group are different on both boxes(neither being root). Any help would be appreciated. --Jeff

I?m trying to rsync a 210 GB Filesystem with approx 1.500.000 Files. Rsync always dies after about 29 GB without any error messages. I?m Using rsync version 2.5.5 protocol version 26. Has anyone an idea ? Thank?s Clemens

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

All, Could someone please help me resolve this: [admx:test] $ ls ERR01 ah01 ah02 an01 an02 mp01 mp02 [admx:test] $ ls {an,mp,ERR}* ERR01 an01 an02 mp01 mp02 I want to rsync only the "{an,mp,ERR}*" files across using the following command but do not see the expected results. [admx:test] $ rsync -va --exclude="*" --include="{an,mp,ERR}*" ./*

Howdy, We occassionally get the following error when running our nightly backups: rsync error: received SIGUSR1 or SIGINT (code 20) at rsync.c(229) This happens more on one or two machines than on any of the others. We've looked high and low to see if we're mistakenly sending these signals, but nothing is that we can find. Does anyone know what this might be from? Is it the server