Displaying 20 results from an estimated 20000 matches similar to: "--append option description in manpage typo"
2007 Aug 01
2
--append option description in manpage confusing
[ 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
2007 May 19
1
rsync --append behavior
I am using rsync 2.6.9 in daemon mode under Cygwin, and having trouble
reconciling its --append behavior with that described in the man page:
The man page says that when you use --append, it will update a file by
appending, which presumes the existing data on the receiving side
matches. But when I run rsync with append mode when the existing file
on the receiving side is shorter than on the
2018 Oct 18
0
[Bug 13660] New: State clearly in manpage that --append-verify is an edge-case
https://bugzilla.samba.org/show_bug.cgi?id=13660
Bug ID: 13660
Summary: State clearly in manpage that --append-verify is an
edge-case
Product: rsync
Version: 3.1.3
Hardware: All
OS: All
Status: NEW
Severity: normal
Priority: P5
Component: core
Assignee:
2007 Apr 12
2
error on --copy-dirlinks shortform in manpage
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,
2003 Mar 12
1
patch against manpage
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,
2003 May 15
2
single quotes in the manpage
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
2005 May 19
2
Bug#305932: rsync on a directory transfers the files of this directory
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
2017 Mar 03
2
How do you exclude a directory that is a symlink?
The directory I'm trying to copy from is: /home/blah/dir
The symlink is /home/blah/dir/unwanted_symlinked_dir
On Fri, Mar 3, 2017 at 8:10 AM, Paul Slootman <paul+rsync at wurtel.net> wrote:
> On Fri 03 Mar 2017, Steve Dondley wrote:
>
> > I'm trying to rsync a directory from a server to my local machine that
> has
> > a symbolic link to a directory I don't
2008 Apr 07
1
newbie: rsync 2.6.x problems Cygwin client --> RedHat server
On Mon 07 Apr 2008, S.A. Birl wrote:
>
> Server is running rsync 2.6.1 on RH
> Client is running rsync 2.6.3 on Cygwin (Win2003)
>
> When I connect client to server, I get kicked out after SSH
> authentication. I can manually ssh into the server with no problems.
Is the server running an rsync daemon? If so, why the ssh?
Paul Slootman
2007 May 18
2
files deleted without --delete option
Hello all,
I want to copy all files on the SRC side to the DST side without deleteing
any from the DST side. However, whenever I run rsync the files on the DST
side are deleted if they were deleted from the SRC side. What am I doing
wrong?
I am running the following command:
========================================================
rsync -avz --progress --force --delete-excluded
2002 Apr 16
2
Can rsync update files in place?
I've just subscribed, but a search of the archive doesn't indicate this
has been handled before...
Is there a way to get rsync to not create a new file while transferring
and then rename it, but to instead update the existing file in place,
i.e. simply write those blocks that have been updated and leave the rest
alone?
That would be ideal for what I wanted rsync for, namely updating
2004 Sep 05
1
minor typo fix for 2.6.3 pre 1
I'm sure that someone's gonna complain that parsing the output is messed
up by this patch, but then they should have told about the typo
themselves :-)
--- log.c.orig 2004-08-17 10:25:57.000000000 +0200
+++ log.c 2004-09-05 16:28:42.000000000 +0200
@@ -61,7 +61,7 @@
{ RERR_WAITCHILD , "some error returned by waitpid()" },
{ RERR_MALLOC , "error allocating core
2005 Apr 25
2
How about a --min-size option, next to --max-size
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
2008 Apr 22
0
--append skipping longer files
Hi,
Does anyone know a workaround to get the --append option to do a
non-appending inplace transfer when the reciever is longer than the
sender rather than skipping the file.
This is a common problem for us as most of our log files use an hourly
or daily rollover and the reciever doesn't get updated until the
sender builds up in size.
The only option I can think of is adding a block in our
2005 Apr 22
1
"address" option in rsyncd.conf
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
2009 Oct 05
0
inplace (and append) support for partial-dir
Hi,
I frequently rsync larger files from my rented server to my PC.
Sometimes I have to stop the rsync process and restart it a while after
(e.g. I'm shutting down my PC for the night, ...), sometimes several times
per source file.
I like the two following features:
(1) The unfinished files should stay in a own directory (I call it '.dl').
I'm talking here about the 'temp'
2003 Mar 12
1
patch: typo's and gcc warnings
Two patches:
one to correct the spelling of permissions (in comments, but such typos
disturb me as well), and
one to cast inode and dev to unsigned long before comparing, to prevent
gcc giving a warning "comparison between signed and unsigned".
Paul Slootman
-------------- next part --------------
diff -ru orig/rsync-2.5.6/generator.c rsync-2.5.6/generator.c
---
2003 Dec 20
3
preview release: 2.6.0pre1
OK, I packaged up the current CVS as our first preview release for
2.6.0. You can grab it here:
http://samba.org/ftp/rsync/preview/rsync-2.6.0pre1.tar.gz
The MD5 checksum is:
70e9dea967f083c231b7821ef35aef1b rsync-2.6.0pre1.tar.gz
There is not currently a .sig file for the package, but I'm looking into
that next.
Please test this and let me know if we have any remaining issues
2009 Aug 17
10
ssh failure due to local error
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
2015 Jul 16
1
rsync --link-dest and --files-from lead by a "change list" from some file system audit tool (Was: Re: cut-off time for rsync ?)
On Tue, 14 Jul 2015 08:59:25 +0200, Paul Slootman wrote:
> btrfs has support for this: you make a backup, then create a btrfs
> snapshot of the filesystem (or directory), then the next time you make a
> new backup with rsync, use --inplace so that just changed parts of the
> file are written to the same blocks and btrfs will take care of the
> copy-on-write part.
That's