On Sat, Feb 14, 2009 at 08:53:22PM -0500, Matt McCutchen wrote:
> The attached patch (also in wip/supplementary-groups of my repository)
> adds a daemon parameter to take on the supplementary groups.
I went a little different route than this path by allowing the user to
specify one or more groups
On Mon, Feb 16, 2009 at 09:29:38PM -0600, Kent Vander Velden wrote:
> Is there an alternative format type that lists the file length in a
> human readable format, perhaps optionally if --human-readable is
> specified?
No, nothing like that currently exists. The master branch in git (that
will bec
On Sat, Feb 14, 2009 at 09:29:11AM -0800, Wayne Davison wrote:
> I have decided that we'll try running the list that way and see how
> we like it
Sadly, the rejection mails are way too cryptic to be useful. I will ask
the samba folks if they will consider upgrading to a newer version
On Sun, Feb 15, 2009 at 05:08:36AM -0700, lewis butler wrote:
> This tells everyone the exact length of each password
The docs should actually say that everything after the first line of
the file is ignored. So, feel free to add any text you like after
that. I'll improve the man page to get this
On Wed, Jan 21, 2009 at 10:47:29PM -0500, Matt McCutchen wrote:
> I'm shifting my position on this issue because I've seen several
> problems that would be solved by requiring posters to join the list:
I have decided that we'll try running the list that way and see how
we like it:
Non-member post
On Tue, Feb 03, 2009 at 02:09:38PM +0100, Julian Pace Ross wrote:
> Hi, I have two versions of a file that in theory should be quite similar...
> however, the transfer is taking more or less the same time as though the
> whole file is being transferred.
I'd imagine that you did a local copy withou
On Wed, Jan 28, 2009 at 12:35:05PM +0100, David de Lama wrote:
> rsync -acv --bwlimit=1 --stats --progress --delete
> 192.168.222.82:"/home/test" /backup/rsync0
> Now it takes only about 45sec.
> So I am still wondering. Am I doing s.th. wrong?!
The -c option tells rsync to read the source fi
On Tue, Jan 20, 2009 at 03:25:05PM +0530, Jignesh Shah wrote:
> In "rsync return code: 12" error, what 12 indicates?
The error code is pretty inconsequential compared to the errors that
come before it. See what rsync is actually complaining about, and make
sure you know if there is an issue with
On Tue, Jan 20, 2009 at 10:16:37AM +, Stuart Halliday wrote:
> I suggest that this may be caused by you using two different versions of
> Rsync? Please check that the daemon and client are running the same version.
The only known issues of cross-version incompatibility have been fixed.
If you
On Sun, Jan 18, 2009 at 01:03:29PM +0100, August C. Quint wrote:
> I've created a little script that makes a backup of my home-directory using
> rsync. When I call this script again _all files_ will be copied again.
You should ask rsync to tell you what is going on using the -i option.
If you see
On Wed, Jan 14, 2009 at 02:25:33AM -0500, Matt McCutchen wrote:
> I think I'll take the opportunity to improve the design a bit by
> actually adding a section structure representing the global values of
> section parameters to the global structure
I was thinking we could get rid of the big, must-k
On Thu, Jan 15, 2009 at 06:11:36PM -0600, Harry Putnam wrote:
> In other words the full directory structure minus any plain files.
Right, that's what compare-dest does. It only copies changed files,
omitting all files that haven't changed between the source and the
alternate destination. If you
On Thu, Jan 08, 2009 at 11:29:21AM +0100, Fabian Cenedese wrote:
> --delete-before receiver deletes before transfer (default)
The man page was lagging behind. I've checked in a fix. Thanks!
> Is there a way to take advantage of incremental, even if it means
> running rsync twice?
You c
On Sat, Dec 27, 2008 at 03:35:31PM -0800, Wayne Davison wrote:
> I'll need to work out the right way for the sender to monitor the
> verbose data from the sender throughout the file transfer.
For 3.0.5, I took the easy/safe route of just having the server-receiver
decrease the verbose
I have released rsync 3.0.5. This is another bug-fix release.
To see a full summary of the changes since 3.0.4, visit this link:
http://rsync.samba.org/ftp/rsync/src/rsync-3.0.5-NEWS
You can download the source tar file and its signature from here:
http://rsync.samba.org/ftp/rsync/src/rsyn
On Thu, Dec 18, 2008 at 10:37:43AM -0800, Jonathan Chen wrote:
> rsync --dry-run -aucvvvX --log-file=fly-dryrun.txt /Volumes/airplane/
> /Volumes/plane/flight
> when running the above command, rsync idles with no action.
Apparently this started with 3.0.0. The sending of the file list can
block w
On Thu, Dec 04, 2008 at 05:58:05PM -0600, Larry Hayes wrote:
> I have tried several other combinations of '\'' and single and double
> quoting the entire path or just the filename, with no luck.
There's no such thing as quoting in an include/exclude file. Anything
after an initial -/+ and a space
On Tue, Dec 23, 2008 at 10:22:42AM +1100, Robert Bell wrote:
> we would like rsync to use a hard-link from ../backup.1 in
> preference to a new copy from source/ to backup.0/ .
That's not something that I plan to implement. I'd suggest changing
your naming to always use a new directory, which wil
On Sun, Dec 21, 2008 at 07:58:55PM -0800, Bill Wendin wrote:
> My comment: 2nd run hangs if all files are up-to-date.
You should either switch to the latest pre-release of 3.0.5 (which has
batch-mode fixes) or use --no-i-r.
..wayne..
--
Please use reply-all for most replies to avoid omitting the
On Mon, Dec 22, 2008 at 09:46:40AM +0100, Michal Soltys wrote:
> but ... the dir is not there anymore, thus ENOENT
> (due to opendir failing) and rsync's exit code 23.
Yeah, rsync always generates an error if the opendir() call fails in
send_directory(). The attached patch makes it treat a missi
On Mon, Dec 15, 2008 at 12:20:23PM +0100, Peter Rindfuss wrote:
> The latter is a (partial) ACL from /wzb/user/spura, the "spura"
> person's home dir.
The ACL code uses a array to hold the various ACLs it finds. The
receiver builds a list of the items that the sender sends to it, and is
told inde
On Sat, Nov 22, 2008 at 12:03:55AM -0500, Matthew Monaco wrote:
> no way to get --stats per file?
You can use something like this to see the bytes sent compared to the
file's length:
--out-format='%n%L (%b of %l)'
..wayne..
--
Please use reply-all for most replies to avoid omitting the mail
On Wed, Nov 19, 2008 at 10:13:41PM +0100, AZ 9901 wrote:
> Could it be possible to force rsyncd to do the chdir() after pre-xfer ?
That is not currently possible because rsync wants to tell the pre-xfer
process about the options that the client sent (such as what module is
being requested), and th
Rsync version 3.0.5pre2 is now available for release testing. This is
a bug-fix release.
I hope this is the final pre-release for 3.0.5, so please test this new
release and send email to the rsync mailing list with any questions,
comments, or bug reports.
The changes since 3.0.5pre1:
- Fixed th
On Sat, Nov 15, 2008 at 01:09:20PM -0800, David Rothenberger wrote:
> Does this patch (or a modified version that conforms to POSIX) stand a
> chance of being accepted?
There's a problem with including this in the mainstream version: if we
don't turn //some/path into /some/path, it won't match a
On Sat, Nov 15, 2008 at 01:09:20PM -0800, David Rothenberger wrote:
> Unfortunately, it doesn't fully conform to the POSIX specification because
> it also translates '///' to '//' instead of '/' as required.
An easy fix for that is to change your newly added "if" to this:
if (*f
On Sat, Nov 01, 2008 at 08:29:38AM -0400, Matt McCutchen wrote:
> You are right, the combination of -K, --delete and incremental recursion
> is broken.
I've committed Matt's fix for this into the git repository for both
3.0.5 (which is about to get a new pre-release) and 3.1.0 (the
enhancement bra
On Tue, Nov 04, 2008 at 10:21:31AM -0700, Leon Vanderploeg wrote:
> In the previous version of rsync a /./ in the from file would cause
> the previous path information to be dropped for the destination
> directory. In 3.0.4, it appears the . is being translated into the
> current (working) directo
On Sun, Nov 02, 2008 at 09:39:05PM -0800, kbrault wrote:
> insecure -e option not allowed.
> This account is restricted by rssh.
You should fix or replace rssh. See a prior thread where I posted a
patch to fix the silly command-checking of rssh. If all rssh allows
in is rsync, see the support/r
On Wed, Oct 22, 2008 at 02:05:43AM -0400, Matt McCutchen wrote:
> In incremental recursion mode, the number of files "to check" can
> increase (when new file-list chunks are built) as well as decrease,
> which I found confusing to watch. This patch makes the progress line
> show the number of file
On Tue, Oct 21, 2008 at 10:02:42AM +1100, Ronnie Sahlberg wrote:
> This patch provides extensions to RSYNC to map to and use filesystem
> extensions present in the IBM GPFS cluster filesystem.
Thanks for the patch! I have looked over your changes, and I have some
preliminary feedback:
- When a
On Fri, Oct 17, 2008 at 03:34:03PM +0800, Thomas Gutzler wrote:
> I had another rsync hang. I've attached a text file with the stack
> traces you asked for and some other info.
The generator backtrace shows that it is waiting for the receiver to
finish some files before going on. This attempts to
On Thu, Oct 16, 2008 at 12:41:07PM -0500, Todd Rinaldo wrote:
> Rsync works well for this purpose, but it would be nice if we could
> rsync to/from a tar (or other archive format) file.
It would be better to leave such things to an external tool, such as a
fuse filesystem. A read-only one that I
On Tue, Oct 14, 2008 at 08:24:31AM +0700, BuraphaLinux Server wrote:
> rsync: hlink.c:273: check_prior: Assertion `node->data != ((void *)0)' failed.
Everywhere in the hlink.c code that sets a node, sets a data value and
ensures that it is non-zero, so there's no code path in the logic that
can al
On Tue, Oct 07, 2008 at 05:03:44PM -0400, Hasenbalg Michael (JuP/TEF-MIS) wrote:
> In regards to one of the 'current issues and debugging' - Why does my
> transfer die with something like the following error? I found that this
> error occurs also if the path
> log file = /xyz/abc/rsyncd.log
> in y
Rsync version 3.0.5pre1 is now available for release testing. This is
a bug-fix release.
Please test this new release and send email to the rsync mailing list
with any questions, comments, or bug reports.
To see a full summary of the changes since 3.0.4, visit this link:
http://rsync.samba.or
On Thu, Oct 09, 2008 at 06:44:20PM +0100, Giuliano Procida wrote:
> (Server) Protocol versions: remote=7680, negotiated=30
> protocol version mismatch -- is your shell clean?
This will be fixed in the next version. Until then, you can work around
the problem by supplying a "." after the "host:" a
On Thu, Oct 09, 2008 at 03:29:04PM +0100, michael wrote:
> and this is when I've tried both of
> a) /usr/bin/rsync --daemon -v
> b) sudo /sbin/chkconfig rsync on
Fedora supplies an /etc/xinetd.d/rsync file that defaults to off. Using
your b command should turn it on and sighup xinetd. If you go
On Mon, Oct 06, 2008 at 11:28:31PM +0200, Bas van Schaik wrote:
> Since this is a production environment I'd like to stick to 3.0.3
> (which is already newer than I'd like to use...) in stead of upgrading
> to 3.0.4, unless have very good reasons to believe it is really fixed
> in that last version
On Sun, Oct 05, 2008 at 06:47:47AM +0200, Shachar Shemesh wrote:
> The reason this is brought up is because I'm using rssh
> (http://www.pizzashack.org/rssh/) as the user's shell to limit that
> user to only be allowed to run rsync.
I looked at the source, and created a patch to make it just requi
On Sun, Oct 05, 2008 at 06:47:47AM +0200, Shachar Shemesh wrote:
> Rssh, however, prevent the passing of the "-e" option to rsync, as it
> claims (with some amount of justification) that this option allows
> someone to cause rsync to run any command at all, escaping the
> limitations imposed by rss
On Mon, Sep 29, 2008 at 02:47:53PM -0700, Wayne Davison wrote:
> reordering the args in the ifs so that an underflow can't trigger a
> spurious successful test.
Actually, my change isn't good enough, since an underflow with the "if"
vars reordered should actually indic
On Mon, Sep 29, 2008 at 09:49:26AM -0500, Mike Bombich wrote:
> 1) cmp_time (util.c) doesn't check for negative values provided in file1 or
> file2. If file2 is positive, and file1 is negative, and
> absolute_value(file1) > file2, cmp_time returns 0, even though the times
> are obviously differ
On Sun, Sep 28, 2008 at 03:39:06PM +0800, Zhiming Zhou wrote:
> rsync -a --link-dest=/remote/old /tmp/myfile [EMAIL
> PROTECTED]::backup/remote/new
As long as remote/old is a path inside the backup module, and is on the
same filesystem as the remote/new path inside the backup module, it
should wo
On Sat, Sep 27, 2008 at 01:21:42PM -0700, Chris Roehrig wrote:
> Your patch didn't fix it, but this one seem to work:
Yup, that is indeed the right thing to do. Thanks!
..wayne..
--
Please use reply-all for most replies to avoid omitting the mailing list.
To unsubscribe or change options: https
On Fri, Sep 26, 2008 at 05:42:40PM -0700, Chris Roehrig wrote:
> I've been getting spurious unnecessary copying of files on OSX when using
> the crtimes patch and the --crtimes -H options (version 3.0.4).
This appears to be a lack of initializing the stat_x crtime value to 0 in
the hlink.c code.
On Tue, Sep 23, 2008 at 01:04:50PM +0200, Paul Slootman wrote:
> In debian bug #498083 (http://bugs.debian.org/498083) someone is getting
> segfaults reasonably consistently, however when using - it doesn't
> happen...
Much appreciated! That info made me immediately think that there was an
xa
On Sat, Sep 20, 2008 at 12:49:08PM +0530, Rajiv Nair wrote:
> Please help to get rid of passwd.
When contacting a daemon (as your command indicates), you can put the
password in a file, and use the --password-file=FILE option. Set the
permissions as tightly as possible to keep it secret.
..wayne
On Sat, Sep 13, 2008 at 07:10:53AM +1000, Quey wrote:
> maybe something like a --chown user.group
There is a diff in the patches directory that allows you to do this.
If you apply patches/usermap.diff, you can use a command like this:
rsync -av --usermap=*:someuser --groupmap=*:somegroup /src/ /d
On Wed, Sep 10, 2008 at 04:44:02PM -0700, Wayne Davison wrote:
> The attached patch should fix things.
That patch accidentally reverted an ability to transform a relative
module path into an absolute one when chroot was not enabled. The
attached patch fixes this.
..wayne..
--- a/clientserve
On Wed, Sep 10, 2008 at 03:50:46PM +0200, Paul Slootman wrote:
> Apparently in pre-3.0.0 versions '%P' would log the actual path as
> specified in the module entry in rsyncd.conf, but now it's apparently
> relative to the chroot...
Yeah, that appears to have happened in the security release that a
Sorry for the slow reply -- I marked your message for more in-depth
study, and failed to get back to it until now.
On Sun, Jun 22, 2008 at 08:01:16PM -0400, Phil Vandry wrote:
> I have long wished for a feature in rsync to detect files that have
> renamed on the sender side since the last time a s
On Tue, Sep 09, 2008 at 01:08:57PM +0200, Jan Thielmann wrote:
> #[sender] i=0 /u/prak28 dir1 mode=0755 len=288 uid=3007030 gid=0 flags=5
That mode is totally bogus. For dir1 to be a dir, it should have mode
040775. If it were a regular file, it should have mode 010775. So, you
should investiga
I have released rsync 3.0.4. This is a bug-fix release with the only
"enhancement" being the adding of a way to interact with an overly-
restrictive server that refuses rsync's behind-the-scenes use of the
-e option.
To see a full summary of the changes since 3.0.3, visit this link:
http://rsy
On Mon, Aug 25, 2008 at 04:43:29PM +0200, Thomas Ebert wrote:
> rsync: stat
> "/home/thomas/DiskStation/Thomas/backup/molungus-root/2008-08-25/usr/share/terminfo/L/LFT-PC850"
>
> failed: No such file or directory (2)
> usr/share/terminfo/l/lft => usr/share/terminfo/l/lft-pc850
> rsync: link
> "
On Tue, Sep 02, 2008 at 09:11:22AM -0400, Simo Sorce wrote:
> The advantage of using a glibc function is that it uses the correct
> locale settings for the thousands separator and does not require
> guessing.
Rsync has to be able to run on systems that don't use glibc, so I
decided not to use that
On Sun, Aug 31, 2008 at 10:44:11PM -0400, Matt McCutchen wrote:
> Wayne, you might want to consider applying this even though the
> immediate problem is solved.
Yeah, I had noticed that lack-of-negative number-handling deficiency
when I was working on an enhancement for 3.1.0 to output numbers in
On Sat, Aug 30, 2008 at 12:52:42AM -0700, dfirth wrote:
> Is there a reason I get the following strange characters in my log file?
What rsync version are you using? I've never seen that before. Also,
which of the various PRINTF defines are defined in your config.h file?
% fgrep PRINTF config.h
On Mon, Aug 25, 2008 at 06:58:38PM +0200, Bacchella Fabrice wrote:
> This patch only add gssapi authentication, I wanted it to be simple and
> fast to code.
Thanks! I've saved it off and will give it a look soon.
..wayne..
--
Please use reply-all for most replies to avoid omitting the mailing
On Sun, Aug 24, 2008 at 05:54:12PM +0200, Leslie Jensen wrote:
> rsync -tv --files-from="my list of files" /home/user/configuration/
You're missing a path in that command, presumably the source path.
All names in a files-from file are relative to the source path, but
you can use "/" if you want th
On Wed, Aug 20, 2008 at 10:32:23AM -0400, Carney Mimms wrote:
> COMMAND="sudo /usr/local/bin/rsync $OPTS $EXCLUDES $DIRS $BACKUPDIR"
That's a sudo issue, since sudo runs the command and splits the args on
spaces. You need to either add extra backslashes (\\\ for every \), add
extra quoting (e.g.
On Fri, Aug 15, 2008 at 05:28:43PM +0200, Rob klein Gunnewiek wrote:
> ERROR: out of memory in flist_expand [generator]
With -vv, you should be seeing messages like this:
[generator] expand file_list pointer array to N bytes, did move
That will tell you what the last realloc attempt was before t
On Mon, Aug 18, 2008 at 11:57:43AM -0400, [EMAIL PROTECTED] wrote:
> which gives me the error "Killed: 9" when it terminates.
That's not an rsync error, but is likely to be a shell message that says
that something else killed rsync. I'd suggest checking the system log
files and/or process history
On Mon, Aug 18, 2008 at 10:36:18AM -0500, [EMAIL PROTECTED] wrote:
> In other words, I can't wait until the first run has completed the
> large copy to begin copying additional files. I want to start a
> second, third, fourth, etc copy that begins working on any additional
> files that may have be
On Tue, Aug 12, 2008 at 11:46:11AM -0700, Aleksey Tsalolikhin wrote:
> How much memory will rsync use? I didn't specificy any of the
> switches that disable incremental recursion.
It depends on your options, and possibly on the maximum number of files
in a directory. I've seen a recursive scan
On Tue, Aug 05, 2008 at 08:55:10PM -0400, Matt McCutchen wrote:
> I've been working on this; my patch in progress is attached.
Thanks, Matt! I've saved that off and am looking into integrating it
for the trunk (and adding a merge-file debugging category). I've
fiddled with it a bit so far, and w
On Thu, Aug 07, 2008 at 10:42:57PM +0700, BuraphaLinux Server wrote:
> rsync: hlink.c:271: check_prior: Assertion `node->data != ((void *)0)' failed.
That should only be possible if rsync ran out of memory. Here's a
missing check for that that you can try out.
..wayne..
--- a/hlink.c
+++ b/hlink
On Thu, Aug 07, 2008 at 10:53:34AM +0200, Rob klein Gunnewiek wrote:
> However, even though I exclude this directory, rsync still attempts to
> access it:
Yes, this has come up before. The current exclude code wants to know in
advance if the items is a directory so that it knows which rules apply
Rsync version 3.0.4pre2 is now available for release testing. This is a
bug-fix release with the only "enhancement" being the adding of a way to
interact with an overly-restrictive server that refuses rsync's
behind-the-scenes use of the -e option.
I hope this will be the final pre-release prior
On Sat, Aug 02, 2008 at 08:26:47AM -0500, Neil Gunton wrote:
> However if I reinstall Linux, and try to restore from the backup hard
> drive, the owner permissions get all mixed up, I assume since the
> numeric uids don't match up with the equivalent usernames any more.
One option is to try userma
On Wed, Jul 30, 2008 at 04:33:04PM +0300, Shachar Shemesh wrote:
> Rsync does have some CPU inefficient behavior for especially large files.
> However, it should not happen at the block size you are using (assuming the
> files are fairly identical). Try increasing it a little further, to 1638400
On Tue, Jul 29, 2008 at 10:47:52AM +0530, Shashi Kanth Boddula wrote:
> path = /data/Knowledge Centre
My only addition to what has already been said is to quote the manpage:
Leading and trailing whitespace in a parameter value is discarded.
Internal whitespace within a parameter value is reta
On Fri, Jul 25, 2008 at 03:37:52PM -0300, Manuel Kissoyan wrote:
> Wondering how i can trace to the problemim backing up many servers
> and on all of them im seeing this error.
Look at the stderr output for earlier errors that were output. Things
like lack of permissions opening a directory o
On Fri, Jul 25, 2008 at 12:24:08PM -0700, [EMAIL PROTECTED] wrote:
> Discovered that the -n option had been changed to not work unless
> -v is added.
No, -n works fine w/o -v, as it shows you exactly what would be output
by the command if -n were not specified. This is a fix over earlier
versions
Rsync version 3.0.4pre1 is now available for release testing. This is
a bug-fix release with the only enhancement being the adding of a way
to interact with an overly-restrictive server that refuses rsync's
behind-the-scenes use of the -e option.
Please test this new release and send email to the
On Fri, Jul 11, 2008 at 10:10:16AM -0400, Jeff Woods wrote:
> --bwlimit=17 --partial --append
You only want to use --append if you can guarantee that the files will
not have any changes in the existing data on the receiving side. A
modern rsync does not compute a full-file checksum for --appe
On Fri, Jul 11, 2008 at 09:58:21AM -0300, Jeff MacDonald wrote:
> Everytime, it seems to die with something like this [...]
> rsync error: some files could not be transferred (code 23) at main.c(1506)
That's not "dying", that's completing its run and letting you know that
some files could not be
On Fri, Jul 11, 2008 at 04:22:04PM +0100, Tiago Marques wrote:
> I was already using the -d option, it download the subdirs also.
You also need to not use -r (e.g. either expand -a and omit -r, or
specify --no-r).
..wayne..
--
Please use reply-all for most replies to avoid omitting the mailing l
I think it's about time to start adding some new features to rsync 3
instead of just making bug fixes, so I'm planning to starting work on
version 3.1.0. This will start the use of a new version numbering
idiom where feature releases increment the sub-version number, while
patch releases continue
On Fri, Jul 04, 2008 at 02:59:20PM -0400, Brian Lindholm wrote:
> it would be even better if it only rewrote the portions of large files
> that had actually changed instead of resending the entire file.
You can use --no-whole-file with --inplace (since rsync's default update
method is to write out
On Fri, Jul 04, 2008 at 05:08:41PM -0400, Matt McCutchen wrote:
> Use --recursive and then exclude the stuff you don't want, e.g.,
> --exclude='/*/' to exclude all subdirectories.
You can also use -d (--dirs) instead of -r (--recursive). That makes
rsync transfer just the contents of a specified
On Fri, Jul 04, 2008 at 08:11:36PM +0100, Tiago Marques wrote:
> rsync --delete-before -v -tvlpr
> rsync://rsync.sabayonlinux.org/SabayonLinux/* ./ --dry-run
Check out the manpage on the --delete option. The very first paragraph
tells you why you shouldn't be using a wildcard (*) there:
ht
On Fri, Jul 04, 2008 at 10:08:49AM +0200, [EMAIL PROTECTED] wrote:
> Does anyone have an idea how to "change" to a directory on remote maschine
> to use relative paths (-R) ?
Starting with 2.6.7 you can insert a dot dir into any source path to
indicate where the duplicating of directories starts:
I have released rsync 3.0.3. This is a bug-fix release that contains no
new features.
To see a full summary of the changes since 3.0.2, visit this link:
http://rsync.samba.org/ftp/rsync/src/rsync-3.0.3-NEWS
You can download the source tar file and its signature from here:
http://rsync.samb
On Wed, Jun 25, 2008 at 04:26:08PM -0400, Aaron Davies wrote:
> My guess is that the subdirectories of the target directory not
> mentioned in the --files-from file are not considered part of the
> sync and are thus not considered for deletion.
No, not if you've explicitly specified -r (since -a d
I have made rsync 3.0.3pre3 available for release testing. This is another
bug-fix release, with the only "enhancements" being made to the manpages and
the testsuite.
These are the changes that have happened since 3.0.3pre2:
- Fixed the sending of xattr directory information when the code find
On Sun, Jun 22, 2008 at 06:09:02PM -0400, Matt McCutchen wrote:
> An attempt at a patch is attached; Wayne, please look into it.
Looks good to me. I've applied it to the source.
..wayne..
--
Please use reply-all for most replies to avoid omitting the mailing list.
To unsubscribe or change optio
On Sun, Jun 22, 2008 at 10:35:07AM +0300, Ciprian Dorin Craciun wrote:
> I found a little bug in the rsync v3.0.2 install, that is if you
> separate the build (output) folder from the source folder, the man
> files fail to install [...]
Thanks. The latest source has this fixed.
..wayne..
--
On Thu, Jun 05, 2008 at 08:22:09AM +0200, Peter Breitenlohner wrote:
> However, "cp -p" and "touch -r" round to the nearest second.
Can you try out the attached patch and let me know if it fixes the
rounding issues?
..wayne..
--- a/testsuite/backup.test
+++ b/testsuite/backup.test
@@ -36,7 +36,7
On Sun, Jun 15, 2008 at 09:36:30AM +0200, Michal Soltys wrote:
> would it be allright to submit a small manpage diff, to add some
> details about difference between delete-delay and delete-after ?
Diffs are always welcomed. Please feel free.
..wayne..
--
Please use reply-all for most replies t
On Tue, Jun 10, 2008 at 02:42:25PM -0700, becca23 wrote:
> but I would like to know if there is an option, whether in the rsync
> command or placed in the rsyncd.conf file where I can call a script
> that runs each time rsync executes?
See the "pre-xfer exec" and "post-xfer exec" daemon parameters
On Tue, Jun 10, 2008 at 09:58:34PM +0200, Michal Soltys wrote:
> Still, in that case - what's the benefit of using --delete-delay option ?
It is useful for things such as --delay-updates --delete-delay (to have
all updates happen more rapidly at the end), and the option avoids an
extra dir-scan de
On Tue, Jun 10, 2008 at 04:41:42PM +0200, Michal Soltys wrote:
> rsync -aHx --delete-delay --filter="dir-merge, .rf" /src/ /dst/
> ...testfile will be removed, unless .rf (with above rules) already exists
> on the receiving side.
Yeah, that is how it currently works. The --delete-delay option de
On Tue, Jun 10, 2008 at 03:03:23AM -0700, GiveMF wrote:
> So I want to sync from the dev directory (which doesn't have .svn
> directories) to one that does.
An exclude does two things: it prevents files that match from being
transferred from the sender, and it protects files that match from being
On Fri, Jun 06, 2008 at 04:14:45PM -0300, Manuel Kissoyan wrote:
> This is the one from the server where we are running the rsync command
> and where we backup the other server:
That's just the client. You also need to see what the server is doing.
You should attach to all 3 rsync processes, 2 on
On Wed, Jun 04, 2008 at 05:25:06PM -0300, Manuel Kissoyan wrote:
> rsync error: timeout in data send/receive (code 30) at io.c(233)
> [sender=3.0.0pre2]
Are you using a --timeout option or a timeout parameter in a daemon
config? If so, try increasing that value. If not, you should check to
see
On Wed, Jun 04, 2008 at 03:03:17PM +0100, Steven Hartland wrote:
> zone/english/mp_carentan1.ff
> ^CKilled by signal 2.9.72kB/s0:00:55
This looks like a system message overwriting the display, which rsync
can't control. We could switch over to writing \r at the start of each
progress message
On Wed, Jun 04, 2008 at 02:56:40PM +0100, Steven Hartland wrote:
> flist.c:874: warning: comparison between signed and unsigned
> flist.c:876: warning: right shift count >= width of type [...]
These errors were due to off_t being 32-bit, which wasn't handled well.
I have improved that code, and th
On Mon, Jun 02, 2008 at 07:31:02PM +0200, Peter Breitenlohner wrote:
> (1) With the Linux kernel >=2.6.20, "make check" occasionally fails, due to
> subsecond timestamps sometimes being truncated and sometimes being rounded
> upwards (both on i686 and x86_64).
Rsync doesn't do any rounding, so I d
On Sat, May 31, 2008 at 10:20:35AM -0700, Stuart Anderson wrote:
> I would like to be able to use shell globing to generate a long list
> of source directories but still allow rsync to filter out some of those.
That is supported, but you must exclude an item you've specified, not an
implied compon
501 - 600 of 2912 matches
Mail list logo
