similar to: (patch) fix for spinning child processes in daemon mode

Hi, If anyone is interested, the included patch to rsync-2.6.2 allows you to specify the port number for an rsync server as a global option in rsyncd.conf with 'port = <N>' (where <N> is your favorite port number). Note that this parameter only takes effect when the server is started, not when clients connect. Also, specifying the port in rsyncd.conf takes precedence

I've been running rsync-2.4.2 with an old patch of mine for some time for backup purposes. Due to the recent remote bug, I thought it was time to upgrade, even if the host was behind a firewall. So I dug up the old patch (2.5.2 version attached), that I think I sent ages ago to this list as well. It does the following: (1) Firstly, the only sensible way to run something as

Hello list, We discovered that it was impossible to compile Samba 1.9.16p10 on SCO Openserver 3.2.2 (native compiler). Here's a small patch that fixes this problem: ----cut here---- *** includes.h.orig Sun Feb 23 04:26:40 1997 --- includes.h Mon Jun 30 16:18:27 1997 *************** *** 668,692 **** #include <prot.h> #define crypt bigcrypt #endif - #ifndef EVEREST -

appro@fy.chalmers.se wrote: > > No, it's not:-) > > static int sig_pipe(void) > { > BlockSignals( True, SIGPIPE ); > > DEBUG( 0, ("Got SIGPIPE\n") ); > if ( !is_daemon ) > exit(1); > BlockSignals( False, SIGPIPE ); > #ifndef DONT_REINSTALL_SIG >

I have attached a patch that adds 4 options to rsync that have helped me to speed up my mirroring. I hope this is useful to someone else, but I fear that my relative inexperience with rsync has caused me to miss a way to do what I want without having to patch the code. So please let me know if I'm all wet. Here's my story: I have a large filesystem (around 20 gigabytes of data) that

Hello everyone! I didn't find anything in the archives that seemed similar (same error, different offending lines of code). I'm having an issue with rsync on a couple of my servers. A couple of others run just fine but 2 of them give me the same message (see below) when I try to do backups from one server to these linux boxes. All of the linux boxes are the same and have the save

https://bugzilla.samba.org/show_bug.cgi?id=5078 Summary: Unable to use Win32 device paths with --files-from Product: rsync Version: 2.6.9 Platform: x86 OS/Version: Windows XP Status: NEW Severity: major Priority: P3 Component: core AssignedTo: wayned@samba.org ReportedBy: greg@bolshaw.me.uk

tridge and Wayne in particular: I checked in this patch, which is meant to consolidate the ones from both of you for handling EOF in a modules list. The idea is that we need to handle servers that just close the socket rather than sending a nice ending token, but we want to keep EOF detection on in general. (The IO code is such a mess!) -- Martin Index: clientserver.c

Hi. Here's a patch for copying the atimes of files when -t/--times is given. I bumped the protocol to 29 since it sends more data over the wire. It obviously does not send the atime if it's sending data to an older rsync version. It passes all the tests (including the added atime.test) for me on a: Linux Debian/3.0 gcc 2.95.4 (debian), glibc 2.2.5 system. Any questions/feedback? I

We use rsync to provide an rsync share on a linux server with a javascript program on Windows clients which ensures all client data is backed up each morning. After making no progress with my posting last month regarding making a module upload only to prevent someone from manually downloading the rsync share obtaining other users work (exclude = * wasn't possible because we need --delete to

Dear List, I'm using rsync to sync my data, see below command. And I met this error? I think it might be due to 2.6.9 and 3.0.5 compatible issue. So how to solve the problem? Thanks. rsync -vrtopg --progress --delete --password-file=rsync-password /path/on/pc root@192.168.0.202::destination building file list ... 151804 files to consider rsync: push_dir#1 "/" (in maps) failed:

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

Hi, Background : I am using rsync to push/sync FTP uploaded files from master server to slave servers. On slaves the full directory path of each file doesn't exist so rsync is unable to sync it and there a no options in rsync to do something like "mkdir -p/install -D -d" on destination before sync file. N.B. I don't want to do a full sync of the root/home directory every time a

> Just curious: what about the rsync+ patch? Thanks for the reminder. I've just committed Jos's rsync+ patch onto the "branch_mbp_rsyncplus_merge" branch. If it works OK and nobody screams I will move it across onto the main tree tomorrow or Wednesday. I see the patch doesn't add documentation about the new options to the man page, so we should fix that in the future.

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

I am trying to use rsync for making snapshots, sharing hardlinks at the destination using the --link-dest option. In conjunction with this, I would like for --dry-run to report some reliable-ish number for how much space it is going to consume at the destination so that I can arrange to free such space prior the launching rsync "for effect". Right now, that isn't working: #

Hi all. I'm getting the following error when using rsync: nice -n 20 rsync -e "ssh -p30000" --recursive --verbose --verbose --checksum --times --modify-window 2 --port=31000 --dry-run /cygdrive/f/bkp/Doc/Builds/Buildsheets/ MYUSERNAME@MY.SERV.ER.IP:TESTDIR opening connection using ssh -p30000 -l MYUSERNAME MY.SERV.ER.IP rsync --server -vvntrc --modify-window=2 . TESTDIR

I posted a patch a few days ago that adds copying of atime. At that time, it was just enabled with -t/--times. After some time, we have figured out that that choice might not have been the best. Here's a new version of the patch (relative to CVS) that adds -A/--copy-atime instead. It also includes a test case. Any feedback on this patch and/or the previous one that I posted?

Hi, I'm trying to set up rsync, with the transfers originating from a Win2K box and going to a Linux box. Both boxes are on my home LAN, so ssh is not required; I thought I would simply use the rsync protocol. I set up xinetd on my Linux box to start a rsync server when needed. My first attempts at a test run failed like so: $ rsync -a /cygdrive/c/installs/palm rsync://192.168.2.3/palm

https://bugzilla.samba.org/show_bug.cgi?id=9502 Summary: Deamon deadlock at stop (SIGINT caught) Product: rsync Version: 3.0.7 Platform: x64 OS/Version: Linux Status: NEW Severity: normal Priority: P5 Component: core AssignedTo: wayned at samba.org ReportedBy: jurij at ocslab.com