similar to: unable to connect over ssh when using an other user than root

I set up ssh without authentication on both servers and I have tested it fine. When I do this: #/usr/local/bin/rsync --rsh /usr/local/bin/ssh --rsync-path /usr/local/bin/rsync remote_server::test /home/test rsync: unable to open configuration file "rsyncd.conf": No such file or directory rsync error: syntax or usage error (code 1) at clientserver.c(502) rsync: connection unexpectedly

Rsync team, and interested parties: i was attempting to get rsync to launch from tcpserver[0] (an inetd replacement from djb) and log to stderr for logging via multilog[1] (syslog replacement by djb) and i was unable to get it to log to stdout/ stderr at all. [0] http://cr.yp.to/ucspi-tcp/tcpserver.html [1] http://cr.yp.to/daemontools/multilog.html i have attached a patch that allows

Hello, Rsync is working great for me right now, using version 2.6.5 on two Solaris 9 V100 servers. Box A is the source and box B is the destination, and also box B is my rsync server box. Box A is a rsync client. Yesterdar from Box B I pulled 250 meg just fine from box A with rsync. Today from the client I want to just copy over to the server what files have changed today. So my command

I'm getting an error trying to pull a file with ssh/rsync: $ rsync -e 'ssh -i .ssh/id_rsa' test@server.com::www/index.html index.html rsync: unable to open configuration file "rsyncd.conf": No such file or directory rsync error: syntax or usage error (code 1) at clientserver.c(502) rsync: connection unexpectedly closed (0 bytes read so far) rsync error: error in rsync

Greetings - In my logwatch report this morning I noticed reference to an attempt to connect to rsync from an external IP address. It doesn't appear that the connection was successful based on correlating information between /var/log/secure and /var/log/messages. But I am looking for some suggestions for implementing more preventative measures, if necessary. The log information from

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

Hi Folks -- I've recently had the need to add a piece of functionality to rsync that allows one to run 'rsync --daemon' (rsync in "rsync server" mode) over SSH. My main goal was to be able to use some of the features from rsyncd.conf(5) (notably modules) while still using SSH for authentication and network transport. Background: I wanted to have the capability of setting

Hi everyone, I'd like to propose a patch for review. It enhances rsync when patched and compiled with slp support. It adds a new global boolean option, 'disable slp', which can be used to disable SLP advertisements at runtime. The idea behind this patch is to allow distributors to build rsync with SLP support compiled in, but to allow the users to turn it off without recompiling

I had rsync2.5.5 running fine ona RedHat Linux 8 system. I downloaded the rsync2.5.6 code and it compiled with no problems. However, operations which worked before are now failing. Here is my rsyncd.conf file uid = nobody gid = nobody # use chroot = no max connections = 4 syslog facility = local5 pid file = /var/run/rsyncd.pid motd file = /etc/rsyncd.motd [ftp] path = /var/ftp/pub

Hello, I just posted this a few days back and my email got totally messed up so I don't know for sure if there was any reply yet to this. If there was I would be glad if someone just could forward that to me. Thank you in advance, Stephan Hello, I downloaded that win version of rsync and I have a small question: How can I do one of the following: 1.) Add multiple syncronisation

I install rsync in computer and run it as a daemon successfully, but when I run rsync command on another end to connect it. There is a error. The output is : opening tcp connection to 192.168.0.43 port 873 rsync: failed to connect to 192.168.0.43: Connection refused _exit_cleanup(code=10, file=clientserver.c, line=93): entered rsync error: error in

https://bugzilla.samba.org/show_bug.cgi?id=13113 Bug ID: 13113 Summary: receive_xattr heap overflow when prepending RSYNC_PREFIX Product: rsync Version: 3.1.3 Hardware: All OS: All Status: NEW Severity: normal Priority: P5 Component: core Assignee: wayned

3.0.0pre2: non-recursive remote listing breakage Looks like pre1's fix broke something else. I noticed this when listing module/directory contents on servers known to be running versions 2.5.7 & 2.6.3. Not having (full) access to them, I replicated the errors using 2 machines on my home lan. # the machines lithium.elements.lan: the client. rsync 3.0.0pre2 for all tests.

Hi, i have sporadic connection problems with my rsync server. I have _no_ firewall involved and there is _no_ max connections set. rsync on the clients is started from cron via a bash script. There's also no permission problem. rsyncd runs as daemon (is not started from inetd). It sometimes works, but every third or fourth rsync fails with this message: rsync: failed to connect to

Dear all: In fact, even I add the user in the command, the rsync`s error is still appearing: >./bin/rsync -avz tong@192.168.1.30:/BGI/UCSC-mirror/bin/rsync-2.5.4/man ./backup-3000/ rshd: 0826-813 Permission is denied. rsync: connection unexpectedly closed (0 bytes read so far) rsync error: error in rsync protocol data stream (code 12) at io.c(151) another try: >./bin/rsync -avz

Hello. I'm trying something from the rsync man page and it is failing. From http://samba.anu.edu.au/ftp/rsync/rsync.html: -------------------------------------------------------------------------------- CONNECTING TO AN RSYNC SERVER OVER A REMOTE SHELL PROGRAM It is sometimes useful to be able to set up file transfers using rsync server capabilities on the remote machine, while still

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 As far as a backup provider goes I wouldn't expect them to use rsync over SSL unless that were built into rsync in the future (and has been around long enough that most users would have it). I would expect them to either use rsync over ssh secured by rrsync or rsyncd over ssh with them managing the rsyncd.conf file. Either way the server side

Hi folks, This is a patch for rsync 2.6.9 - I'm not sure if this is the proper vehicle for submitting them. It's been working great for us for months, and I hope it's seen as offering useful utility in general. Steve (who is not a subscriber to this list) --- Stephen J Friedl | Security Consultant | UNIX Wizard | +1 714 544-6561 www.unixwiz.net | Tustin, Calif. USA |

Hello? Concerns were raised about the action of shutdown() on Unices - I replied with evidence suggesting that this would not be a problem. I have not heard anything since. If this has to be held over to 2.6.0, fair enough - but please tell me whether itjust needs time, or me to go and fix something??? Thanks Max. BEGIN PATCH diff -mru rsync-2.5.5/clientserver.c

https://bugzilla.samba.org/show_bug.cgi?id=13207 Bug ID: 13207 Summary: rsyncd doesn't send output of failed pre-xfer exec script to client Product: rsync Version: 3.1.1 Hardware: x64 OS: Linux Status: NEW Severity: normal Priority: P5 Component: core