similar to: does --files-from transfer files in the order given?

-q seems to override -v completely, but when combined with --progress, a single newline is output when there are no updates transferred; but if a file *was* updated nothing at all is output. It seems that there might be some short-circuited code when nothing is trasferred, but that a check for quiet mode is skipped somehow. Paul

In the manpage, all occurrences of a single quote (or apostrophe) are preceded by a backslash. This means that these get turned into acute accents by groff; here's the relevant part of the groff manpage: \' The acute accent ; same as \(aa. Unescaped: apostrophe, right quotation mark, single quote (ASCII 0x27). I think all these backslashes should be removed, as the

Hi, A minor bug in the manpage was noticed by a Debian user... (Please keep the 418923-forwarded@bugs.debian.org in the Cc list in replies.) diff -u -r1.399 rsync.yo --- rsync.yo 23 Jan 2007 15:34:43 -0000 1.399 +++ rsync.yo 12 Apr 2007 19:30:17 -0000 @@ -724,7 +724,7 @@ also ignored. Using this option in conjunction with bf(--relative) may give unexpected results. -dit(bf(-K,

Hi, I would like to use the new atxfer (native assisted transfer, see mantis item #3241) , but I've partially been able to make it work. I can receive a call and then having the caller hear MOH while talking with another extension (the one I want to transfer to), but then I can't make the caller and the trasferred talk hanging up or pressing any key combination I'm aware of. My

Hi, I got the following report from a Debian user, about --files-from transferring the contents of a dir (i.e. including the files in it) specified in the input, even thugh the files aren't listed in the input. This happens only when the dir name ends with a slash. I asked him to cook up a script to reproduce this (as it wasn't quite clear to me at first what happened exactly). Any

A trailing slash on a module name has no effect, which is on the one hand logical as it's not a directory name; on the other hand it's not consistent either (as experienced by a user). I suggest at least adding some comment to the manpage where trailing slashes are discussed. Perhaps also mention it in the rsyncd.conf manpage, where perhaps it may be noticed sooner. If I find the time

The manpage states: You may turn off one or more implied options by prefixing the option name with "no-". Not all options may be prefixed with a "no-": only options that are implied by other options (e.g. --no-D, --no-perms) or have different defaults in various circumstances (e.g. --no-whole-file, --no-blocking-io, --no-dirs). You may specify either

I wanted to restrict rsync to listen only on one IP address on a multi-homed system. I put an "address aa.bb.cc.dd" option in the (single) module definition, as the manpage shows that "address" is a module option, not a global one. However, lsof showed that rsync had bound to * instead of the specified IP address. Moving the "address" line to the global part did the

Readers, I have tried the following command: rsync -t *.txt ssh user at remote.machine: and receive the following error: rsync: link_stat "local/machinepath/ssh" failed: No such file or directory (2) rsync error: some files could not be transferred (code 23) at main.c(1031) [sender=3.0.2] My understanding of the manual is that the text files on my local machine should have been

I have this problem. Samba server version 2.2.3a Server Hp 9000 - HP-UX 11.11. Clients W98. Server is used as file-server (config file smb.conf with no particulry changes-I have keeped originally hp-configuration) . I have created personal directory-one for PC-client where I have trasferred file Outlook.pst (OUTLOOK 2000). Casauly file Outlook.pst crashed and I must reload it with Win-prog.

This is a patch against the manpage to clarify what the --perm option does and does not do. Paul Slootman -------------- next part -------------- diff -ru orig/rsync-2.5.6/rsync.1 rsync-2.5.6/rsync.1 --- orig/rsync-2.5.6/rsync.1 2003-01-28 04:11:57.000000000 +0100 +++ rsync-2.5.6/rsync.1 2003-03-07 12:18:19.000000000 +0100 @@ -562,8 +562,13 @@ default\&. .IP .IP "\fB-p,

I just received this bug report on Debian's rsync package. I've verified it. The entry from the manpage: -C [...] Finally, any file is ignored if it is in the same directory as a .cvsignore file and matches one of the patterns listed therein. Here the patterns of a .cvsignore file is apparently used to exclude file outside the directory where the .cvsignore file is found. Any

Hi Wayne, I just got this bug report about rsync 3.0.2 reproducibly crashing, together with a backtrace and a patch; very helpful :-) (Please preserve 477931-forwarded@bugs.debian.org in the CC so that you response is archived in the Debian BTS, thanks.) Paul Slootman On Fri 25 Apr 2008, Kurt Roeckx wrote: > Subject: Bug#477931: rsync: Segfaults syncing the linux kernel archive. > From:

>From the manpage: --csum-length=LENGTH By default the primary checksum used in rsync is a very strong 16 byte MD4 checksum. In most cases you will find that a trun- cated version of this checksum is quite efficient, and this will decrease the size of the checksum data sent over the link, mak- ing things faster. You can choose the

[ see http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=426191 ] The text in the description of the --append option may lead one to believe that files that are shorter on the receiving side won't be updated, due to the following text: ... Only files on the receiving side that are shorter than the corresponding file on the sending side (as well as new files) are sent. ... IMHO

I received the following bug report for the Debian rsync package today. I wouldn't have expected 2.6.4 to refuse to talk to even a 2.6.2 in this way... Perhaps Wayne could comment? Paul Slootman On Tue 26 Apr 2005, Alexey Feldgendler wrote: > > Rsync fails to push filters to the the remote host if the remote rsync > is older than the Debian's. I've tried to connect to a

There's a rather old bug report in Debian's bug tracking system (see http://bugs.debian.org/27126) about wanting to be able to specify the maximum file size, as well as the minimum file size. Here's the text: Sometimes, it's useful to specify a file size range one is interested in. For example, I'd like to keep an up-to-date mirror of Debian, but I currently

On Sat, 2007-11-03 at 18:14 +0000, Wayne Davison committed: > Stop password errors from getting reported as transfer errors. IMO, setting log_got_error back to zero after the password handling is a hack. Here are two possible better approaches: 1. Decide where the real division between setup and transfer errors is (e.g., the beginning of client_run) and reset log_got_error there. 2.

There's a bug reported in Debian about the tty being screwed up by wierd filenames, see http://bugs.debian.org/bug=242300 On the one hand, find will also do this. On the other hand, ls will replace such chars with a question mark. Upon inspection, it appears to be fairly simple to also do this in rsync (in the rwrite() function). Here's a patch. Opinions? Perhaps don't do it

Thank you for your kind explanation. I did it as you mentioned. That is, I set '-march=x86 hello.bc' in the Command Arguments. (I also set my compiled LLC, i.e., LLVM_ROOT_DIR\win32\debug\llc.exe, in the property name Command.) But, when I made a breakpoint in main( ) of llc.cpp and then started to debug I found the 'InputFilename'(llc.cpp:176) is shown like {???}. Therefore it