similar to: AW: Skipping Directory

Rsync maintainers please review rsync bug https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=98740 The code in question is in socket.c in start_accept_loop. The user is getting these warning messages:

I'm trying to understand how to properly setup the /etc/rsyncd.conf file to run an rsync daemon with a secrets file specified in a module - the rsync.conf manpage does not spell it out clearly enough. Rsync server is rsync-2.5.6. If this is my /etc/rsyncd.conf file: ------------------------------------ log file = /var/log/rsync uid = root gid = root [test] uid = rsync1 gid =

Hi, I'm trying to setup automatic sync of files over SSH from node2 to node1. node2 is the "server" and node1 is the "client". I have setup rsync like this on the nodes which runs AIX (4.3.3 and 5.1): 1. Installed rsync from Linux Toolbox (rsync-2.5.4-1.aix4.3.ppc.rpm) on both nodes. 2. Added following to both nodes /etc/services file: rsync 873/tcp 3. Added

Hi, I'm getting below error with "fillup_password_policy" while authenticating users from default domain. [2014/09/30 03:15:26, 10] rpc_client/cli_pipe.c:1432(rpc_api_pipe_got_pdu) rpc_api_pipe: host dev003.namdev.myserv.net returned 16 bytes. [2014/09/30 03:15:26, 1] ../librpc/ndr/ndr.c:251(ndr_print_function_debug) samr_QueryDomainInfo: struct samr_QueryDomainInfo

> From my reading of Atomics.rst, it would be sound to reorder (It does not > say much about load-linked, so I am treating it as a normal load here) > >> store seq_cst >> fence release >> load-linked monotonic > > into > >> load-linked monotonic >> store seq_cst >> fence release > Which would make an execution ending in %old_x = %old_y = 0

Hi, As I can see via path.expand a filename which contains a tilde anywhere gets automatically crippled. +> path.expand("a ~ b") [1] "a /home/user b" +> path.expand("a ~ b ~") [1] "a /home/user b /home/user" I want to open a file regardless whether its name contains any character unless 0. The unix filesystem allow the creation of such files, it

Hi, As I can see via path.expand a filename which contains a tilde anywhere gets automatically crippled. +> path.expand("a ~ b") [1] "a /home/user b" +> path.expand("a ~ b ~") [1] "a /home/user b /home/user" I want to open a file regardless whether its name contains any character unless 0. The unix filesystem allow the creation of such files, it

I'm following up on a bug reported back in May 2002: https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=64689 this bug was also reported to the rsync mailing list: http://www.mail-archive.com/rsync@lists.samba.org/mail5.html#04250 I couldn't find any discussion other than the reporters post describing the problem. Anyway, I just downloaded the new rsync-2.5.6 source, installed

I'm running 'make check' to run the testsuite, and I did it this way so the ssh-basic test would run: # export rsync_enable_ssh_tests=yes # make check I did set up ssh so this would run, and here's what I get for output: POSIXLY_CORRECT=1 TOOLDIR=`pwd` rsync_bin=`pwd`/rsync srcdir="." ./runtests.sh ============================================================

I recently became the new rsync maintainer for Red Hat, and I just completed a review of the current patches that we (Red Hat) maintain for 'rsync'. After removing three unnecessary patches (either already incorporated into rsync-2.5.6, or were outdated and couldn't be applied), we are left with one patch - rsync-2.5.6-sign.patch - which I have attached.