search for: rsync_connect_prog

https://bugzilla.samba.org/show_bug.cgi?id=5020 Summary: hang using RSYNC_CONNECT_PROG Product: rsync Version: 3.0.0 Platform: All OS/Version: Linux Status: NEW Severity: normal Priority: P3 Component: core AssignedTo: wayned@samba.org ReportedBy: Matt_Domsch@dell.com QAContact:...

...RCS file: /cvsroot/rsync/socket.c,v retrieving revision 1.130 diff -u -b -B -w -p -p -u -r1.130 socket.c --- socket.c 11 Aug 2007 16:20:56 -0000 1.130 +++ socket.c 15 Aug 2007 04:17:16 -0000 @@ -300,7 +300,7 @@ int open_socket_out_wrapped(char *host, { char *prog = getenv("RSYNC_CONNECT_PROG"); - if (strchr(prog, '%')) { + if (prog && strchr(prog, '%')) { int hlen = strlen(host); int len = strlen(prog) + 1; char *f, *t; Regards. -------------- next part -------------- A non-text attachment was s...

So I've got this situation where I have two systems connected via a protocol that looks nothing at all like IP, and I'd like to be able to rsync between them. I can, though, open a perfectly normal looking socket through various magic and trickery. I've managed to get rsync to work by using the "rsync --rsh=mymagictransportprogram" style invocation, but for a number of

I've noticed a weirdness in rsync. Let me explain it briefly with an example. Below is a test script: #!/bin/sh cat >rsyncd.conf <<EOF address = localhost use chroot = no hosts allow = localhost [from] path = /tmp/from read only = yes comment = r/o EOF RSYNC_CONNECT_PROG="rsync --address=localhost --config=rsyncd.conf --daemon" \ rsync -av --address=localhost rsync://localhost/from to Looking at the code the daemon should bind to localhost not 0.0.0.0. But strace shows the opposite: alip at harikalardiyari> strace -fe bind ./test.sh ... [pid 7279] bin...

...=============== RCS file: /cvsroot/rsync/testsuite/daemon-gzip-upload.test,v retrieving revision 1.2 diff -u -r1.2 daemon-gzip-upload.test --- testsuite/daemon-gzip-upload.test 24 Dec 2002 07:25:25 -0000 1.2 +++ testsuite/daemon-gzip-upload.test 21 Jan 2003 16:06:42 -0000 @@ -21,5 +21,14 @@ export RSYNC_CONNECT_PROG hands_setup + +# If we are root, we must allow the rsyncd process (which runs under +# a different uid/gid) to write to the destination directory. Source +# directory must be chown'ed as well so that UIDs & GIDs match when +# the source & destination are compared after copying. +if...

https://bugzilla.samba.org/show_bug.cgi?id=5220 Summary: PATCH SUBMITTED: New Feature: stdio model for client Product: rsync Version: 3.0.0 Platform: All OS/Version: Linux Status: NEW Severity: enhancement Priority: P3 Component: core AssignedTo: wayned@samba.org ReportedBy:

...n /usr/local/src/rsync-2.6.9/testtmp.chmod-option/test-rsyncd.conf makepath /usr/local/src/rsync-2.6.9/testtmp.chmod-option/to Running: "/usr/local/src/rsync-2.6.9/rsync -rtvv "/usr/local/src/rsync-2.6.9/testtmp.chmod-option/from/" localhost::test-incoming-chmod/" Using RSYNC_CONNECT_PROG instead of opening tcp connection to localhost port 873 Running socket program: "/usr/local/src/rsync-2.6.9/rsync --config=/usr/local/src/rsync-2.6.9/testtmp.chmod-option/test-rsyncd.conf --daemon" opening connection using --server -vvtr . test-incoming-chmod/ building file list ... done...