similar to: [patch] suggestions for -v option

Unless you suppress all output with the -q option, rsync will always print an initial "building/receiving file list ... done" line. In my opinion, this is a bit superfluous. When I want to see a progress indication, I can use the --progress option. Another issue is the 3-line transfer speed and speedup factor report at the end. So every rsync invocation produces at least four lines of

It would be nice if there were a flag which would have rsync behave like a single -v but which would skip the two line summary info. I do a lot of cron-based transfers and I want to see what gets transferred if anything does, but I'd like it to be entirely silent otherwise. Here is a patch which makes a single -v behave this way. -vv causes it to include the extra info. diff -r -X

Hello, I have written a little script that's would email me all errors. rsync -vah --delete --stats <sources> <destination> > /var/log/sauvegarde/listoffile.log 2> /var/log/sauvegarde/errors.log My problem is i want to have the stats in my mail. Is it possible to redirect --stats to STDERR. I have tryed to do this : /---

[This is a copy of the contents of Debian bug report #147842.] Package: rsync Version: 2.5.5-0.2 Severity: normal Cause ----- - rsync forks a child which in turn forks a grandchild in main.c:do_recv(). - Diagnostics written by the grandchild need to be read by the child using read_error_fd() to be handled properly (with the end result being that they are seen by the user running rsync). -

Since the heap statistics were added, I have viewed thousands of rsync reports (with --verbose and --stats), and not once have I had a need for them. So for me, they're just noise. Here is a 3-part patch to v2.5.6 that treats --stats in a similar fashion to --verbose in that additional --stats will get you more statistics. For this initial case, there's only one additional level of

We use rsync in a Linux installation script. First, the root filesystem of another machine on the network is cloned with "rsync -axzH", and then a few files are updated to give the clone its own identity. This works fine, but last week, the Postfix mailer daemon on a new machine refused to start because some lock files had a link count of 2. It turned out that rsync had created two

I want to create an exact copy of a whole hard disk and to maintain this copy synchronised with the "original" one. The idea is to have a safe backup that allows me, in case the "original" disk fails, to change it by the "clone" disk and start the computer as if nothing had happened. The computer runs Linux. I heard a good option for this purpose is to use dd to

I noticed that the output of "rsync -n" is sometimes truncated. Even when you repeat the same command, the output may be different. I'm using rsync-2.5.5 on a Debian woody system with ext3 file systems. One scenario to reproduce this behavior is someting like this: # rsync -aR /usr/share/zoneinfo /tmp # rsync -n -avRH localhost:/usr/share/zoneinfo /tmp receiving file list ... done

I know "hard" means command will hang if network is broken. But it seems that's not actuate. It's CPU that will hang. Affected scope: I tested it against CentOS 5/6/7, it can be reproduced on all the systems. the debug logs below are captured from CentOS 7 (cifs.ko v2.05) How to reproduce this problem? 1. mount a cifs share with option "hard" 2. stop samba

Hello, i am trying to run Altium Designer Winter 09 on Ubuntu 8.04 with Wine. Altium Designer is a portable application. So their is no need to install. Just run it. It runs very well on my windows partition but not on ubuntu. The message is : "Unable to find DLL C:\Program Files\Altium Designer Winter 09\dxp.exe->winmm.dll" "Launching dxp.exe" "Licensed by VmWare,

Hi, i'm trying to set up an Altium License Server using wine (wine-1.0.1-174-gc4039bd) without success. The process hangs during service start: Code: wine: Unhandled page fault on read access to 0x00000000 at address 0x48f969 (thread 002b), starting debugger... fixme:shell:DllCanUnloadNow stub Unhandled exception: page fault on read access to 0x00000000 in 32-bit code (0x0048f969). Register

Hi, I don't want to start another --files-from war, but I am attaching an updated version of my patch to allow you to specify a list of files to transfer. The normal rsync syntax allows you to specify a list of SRC files to transfer on the command line. This patch adds some new options to allow you to instead supply a file that contains a list of files to transfer. The previous version of

I have hinted in the past of wanting to go to a more selective control of the output of rsync. Here it is. PROBLEMS with the existing --verbose et al. The simple incrementing verbose doesn't allow one to restrict stdout to what actually is of interest. For instance inside dirvish i don't care about directories, or any kind of non-regular file because they show up every time even if

Any votes for/against? ----- Forwarded message from Rik Faith <faith@alephnull.com> ----- Date: Wed, 28 Nov 2001 12:55:29 -0500 From: Rik Faith <faith@alephnull.com> To: mbp@samba.org Subject: rsync patch X-Mailer: VM 6.96; XEmacs 21.1; Linux 2.4.16 (light) Here is a patch that adds rate information (e.g., kB/s) to the --progress display. I just noticed that 2.4.7pre4 is coming

Hiya, I can see it's a regular subject on this list. I, like others wanted to use rsync to synchronise two block devices (as it happens one lvm volume and one nbd device served by qemu-img on a remote host from a qcow2 disk image so that I can keep the old versions) As I couldn't find any report of it being done successfully, I'm just sharing my findings as it might benefit others.

As those of you who watch CVS will be aware Wayne has been making progress in reducing memory requirements of rsync. Much of what he has done has been the product of discussions between he and myself that started a month ago with John Van Essen. Most recently Wayne has changed how the file_struct and its associated data are allocated, eliminating the string areas. Most of these changes have been

Wayne, Please consider the attached patch. This applies to the current CVS, and is independant of patches/local-batch.diff. As a matter of fact, I'm sure it would conflict heavily with local-batch.diff. This version of batch mode has a couple distinguishing features: Write-batch records (almost) the entire sender side of the conversation into one file. ("Almost" because it has

As I reported a while back rsync doesn't handle metadata (permissions and ownership) in dryrun mode. I offered to make a patch and that offer still stands. I didn't have the time for it until now and want to pick it up again. I had some ugly hack back then but I want to redo it in a clean way. I would like some input on my thoughts. IMHO, it would be ideally if the check for dry_run

> 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.

Dear rsync people (particularly Wayne), I noticed that an rsync daemon counts on the client sending a --server option so that am_server gets set to 1. If the client doesn't supply this option, am_server remains 0 but the daemon runs start_server anyway. This is potentially dangerous and might lead to a security hole, although I haven't found one yet. I suggest that the daemon either