On Wed, 2007-12-12 at 17:01 +0100, gorka barracuda wrote:
but, the second time that makes this re-rsync it takes the same time
that the first time...it seems that it doen't make an incremental
backup with our large files... Do you think that the cause could be
the problem of the new optimized
On Tue, 2007-12-11 at 20:45 +0530, [EMAIL PROTECTED] wrote:
Yes Exactly.
When I give;
$ ssh [EMAIL PROTECTED] umask
077
Which explains my problem.
Is this taking from /etc/profile?. B'cos under ~msctrans/.profile, the
umask is set to 022.
How do I by-pass and tell rsync to not
On Mon, 2007-12-10 at 14:32 +0100, Eduardo Juan wrote:
Exactly the same command shows different rsync results depending on the
user executing the rsync.
If I execute rsync as root I get a proper result but if I execute as
user_x there seems to be many files that require updating.
Here is
On Mon, 2007-12-10 at 21:20 +0100, Paul Slootman wrote:
It seems that people running the Debian 2.6.9-5.1 version which has this
patch applied. are running into problems where rsync wants to set
permissions on symlinks.
In the report rsync seems to want to set mtimes, not permissions.
The
On Mon, 2007-12-10 at 22:20 +0100, Olivier Thauvin wrote:
I don't how to really fix into rsync,
except checking uname to get the running kernel's version.
It would seem much more direct to simply attempt the lutimes and ignore
an error of ENOSYS (Function not implemented). I don't think it's
On Mon, 2007-12-10 at 21:53 +, Chris G wrote:
I am using rsync version 2.6.9 protocol version 29 on a Fedora 7
system to backup files to a network drive.
rsync is getting I/O errors when copying maildir files (I'm not sure
if the error is happening with other files but these are the
Doug, you might have figured some of this out already but I want to make
sure you are fully informed:
On Fri, 2007-12-07 at 14:29 -0500, Doug Lochart wrote:
I am going to take this approach and mix it with something else I
thought of but I still have a few questions. I am playing with am
On Fri, 2007-12-07 at 11:18 -0500, Doug Lochart wrote:
I am running an rsync command that will have the --server option
appended automagically by rsync. However I do notice that other
default options go along with it. This is what i am seeing:
rsync --server -vlogDtpr --log-format=%o
On Fri, 2007-12-07 at 12:35 +0530, [EMAIL PROTECTED] wrote:
Curiously, whatever be the file permission it masks the group and
users to 00 and retains the perm for owner.
However, If we add the -p bit to rsync, it's retaining the
permissions.
This is strong evidence that the umask seen by the
On Fri, 2007-12-07 at 14:40 -0600, Marc DeTrano wrote:
I am using rsync 2.6.9 (as currently packaged in Mandriva 2007.1)
Ever since the latest update of the package I have been getting an exit
code of 23 with the output file has vanished: {filename}.
For partial transfers due to vanished
On Thu, 2007-12-06 at 09:55 -0500, Doug Lochart wrote:
Each client creates its own SSH tunnel via port forwarding. The
rsync client then sets the target to localhost and the local port of
the tunnel. The remote end is port 873 of the rsync server machine
with a daemon running. Each user
On Thu, 2007-12-06 at 19:23 -0200, Rivanor P. Soares wrote:
I'm running rsync (2.6.2)
That's pretty old. You might want to upgrade to the latest stable
version, 2.6.9.
I want to sync all .fle files from dir1 to the dir2 and also remove
files from the destination which were removed from the
On Tue, 2007-12-04 at 15:59 -0500, Doug Lochart wrote:
Greetings all. Due to security concerns we are switching our backup
processes from SSH tunnel to rsync daemon to Running rsync over ssh
in --server mode. In daemon mode we had a nice conglomerate log file
of all of the backups that ran.
On Wed, 2007-12-05 at 23:21 -0500, Doug Lochart wrote:
Now I am having another issue and that is passing a log format in the
rsync-path. I can see it is coming over but for some reason a defauly
--log-format=%o is appended after --server is added by rsync. This
effectively overrides the
Forwarded Message
From: Eric Praetzel [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Subject: RSync and large amounts of data
Date: Tue, 4 Dec 2007 09:00:39 -0500 (EST)
Good day Mr McCutchen,
I've posted to the rsync list but nobody replied and you seem knowledgeable.
Can you think
On Tue, 2007-12-04 at 09:37 +1100, Kevin Johnson-Bade wrote:
There are some odd things with rsync where the first triggered rule
philosophy seems to break down, in that an exclude * will override a
preceding include whatever.
Please keep discussion of rsync that may be useful to others on the
On Sun, 2007-12-02 at 15:44 +0100, Alan Franzoni wrote:
I have a folder I share between two computers of mine, A and B. What i
want is to be able to keep it in full sync. If a file is added in A,
it should be added to B when rsyncing, and viceversa. If a file is
updated, it should be updated,
On Sun, 2007-12-02 at 16:47 -0800, KJB1 wrote:
If I try:
rsync -lptgoD -e ssh -i /root/.ssh/rsync-key --verbose --exclude=/*.*
--exclude=*.xml --include=+ */Tariff/
192.168.1.1:/home/e-smith/files/ibays/frogs/files/dbs/
rsync lists the correct files, but if I add the destination like
On Wed, 2007-11-28 at 08:39 -0500, [EMAIL PROTECTED] wrote:
I used both UID and id
[EMAIL PROTECTED] ~]# cat /tmp/rsync.ids
0 0
uid=0(root) gid=0(root) context=root:system_r:inetd_t
I bet that context would do it. Paul's suggestion to use id was a
good one!
Matt
--
To unsubscribe or
On Tue, 2007-11-27 at 17:54 -0500, [EMAIL PROTECTED] wrote:
I am not aware of SE linux running on this system unless centos is
enabling this by default. How do I check? (I know I should not ask...)
I know I should not answer, but run selinuxenabled; echo $?. Zero
means enabled, one means
On Wed, 2007-11-28 at 02:29 -0800, Johan Huysmans wrote:
I noticed it is working with the rysnc-3.0.0-pre5, or at least the protocol
of it. Is it possible to use that protocol for the curren stable release.
No, the protocol is new in rsync-3.0.0* .
Matt
--
To unsubscribe or change options:
Wayne,
Thanks for addressing the concerns. I have some comments:
On Wed, 2007-11-28 at 15:33 -0800, Wayne Davison wrote:
The main purpose for the generated files being in CVS and/or git
(including the magic configure script) is to make the build farm work.
When a human checks out the files
On Tue, 2007-11-27 at 10:11 -0400, Jon wrote:
During testing, I completely removed everything from my testing dir
and then ran an rsync into it from another directory on the same
machine into this directory. When the transfer was complete, I had the
entire /etc /var and /root dirs in my
On Sun, 2007-11-25 at 17:37 -0500, [EMAIL PROTECTED] wrote:
When I run rsyncd from xinetd and try to rsync I will get permission
denied error:
rsync: chdir /home/test failed : Permission denied (13)
That's very bizarre, since the daemon is ostensibly running as root and
the permissions on
On Wed, 2007-11-21 at 12:51 +0100, Tom Hummel wrote:
That would make sense, as the hang seems to be caused by rsync writing
too much data to the network too fast, and stracing rsync would slow it
There's no network involved here.
Yes, I suppose I meant the local pipes among the rsync
On Tue, 2007-11-20 at 14:24 -0500, Steve wrote:
I'm currently using rsync to backup home directories using this:
rsync -avx --delete --backup --backup-dir=/u1/home.bak /u0/home/
/u1/home ${log}
I'm trying to move to snapshot backups using this:
rsync -avx --delete --backup
I would like to elaborate a bit on Paul's response:
On Tue, 2007-11-20 at 18:10 +0100, alex loutrbringa' wrote:
When i launch my rsync command with -i option, i see all my binary
files like this :
-
f..T downloads/binaries/binaryv2.cpt.zip
On Mon, 2007-11-19 at 14:47 +0100, Tom Hummel wrote:
for quite some time I've been using rsync on Windows successfully
syncing ~10k files each day. The rsync is that of Cygwin. The sync
is from one FAT FS to another FAT FS.
For a few days now, rsync hangs in the middle of a transfer of big
On Sun, 2007-11-18 at 17:45 -0500, Eric S. Johansson wrote:
Using some of the techniques you show here, it would be possible to trigger
the
backup process and push the data from the laptop.
Yes, push backups can be done quite elegantly by pushing the new data to
a directory and triggering
On Mon, 2007-11-19 at 11:29 +0100, Nico -telmich- Schottelius wrote:
I suggest you to use ACLs on Linux, so permissions are always correct.
This won't help because Eric is using rsync 2.6.6, which doesn't
consider default ACLs its explicit calculation of a new destination
file's permissions. (I
On Mon, 2007-10-15 at 22:17 -0400, Matt McCutchen wrote:
On 10/15/07, Aaron Digulla [EMAIL PROTECTED] wrote:
This is for a production system which goes online Q1 2008. Should I use
the latest stable version of rsync (2.6.9) or will there be a release of
3.0 until then?
Rsync 3.0.0
On Sun, 2007-11-18 at 00:40 -0500, Eric S. Johansson wrote:
I'm looking to see of it is practical to have an rsync server run a script
after
a transfer finishes.
If you mean the server process invoked over remote shell, you could do
something like this:
rsync
On Fri, 2007-11-16 at 16:37 +0100, alex loutrbringa' wrote:
Until know i synchronized a few directories full of binaries with
--checksum options, it took each time a lot
of time since rsync mdsum each file contained in my directories.
Then I decided to skip --checksum option to let rsync work
On Mon, 2007-11-05 at 06:25 -0700, Rob Bosch wrote:
When I use the preallocate patch and create a 77GB file using the function I
get a CPU spike on the server-side.
I don't think reproducing the CPU spike on Linux will be meaningful
because Linux treats posix_fallocate differently from Cygwin:
On Sun, 2007-11-18 at 18:10 -0700, Rob Bosch wrote:
Matt, I have absolutely no programming skills for developing my own
program! I'd be happy to compile and test a program however.
Attached is the C++ source for a simple program allocate to allocate a
file. Call the program like ./allocate
Wayne,
I have a few more concerns about the git repository:
1. It looks like you retroactively removed all generated files from the
history. This may inconvenience a user who seeks to an older version of
the source code and lacks the magic configure to help regenerate the
files. You also
On Fri, 2007-11-16 at 13:22 -0800, Charles Polisher wrote:
I am experimenting with Matt McCutchen's excellent continusync script,
and I'm having an issue. (My copy of continusync has been modified from
the original
http://mattmccutchen.net/utils/continusync by adding this @ line 227:
setup based on pyinotify, which I believe is
considerably more mature than continusync:
http://lists.samba.org/archive/rsync/2007-August/018329.html
Ask him for a copy of the code.
Regards,
Matt
On Fri, 2007-11-16 at 14:55 -0800, Charles Polisher wrote:
Matt McCutchen wrote:
1. Wait for a short
On Thu, 2007-11-15 at 15:41 +0100, Lucas Meijer wrote:
Can anybody spot my mistake?
mkdir a b c
echo foo a/test
echo foo b/test
rsync -av --compare-dest=b a/ c/
Relative --*-dest paths are interpreted relative to the destination
directory (as stated in the man page), so you should use:
On Tue, 2007-11-13 at 17:42 +0100, Paul Slootman wrote:
On Tue 13 Nov 2007, Ismaël BALLO wrote:
I've googled but not found exactly what I want.
I want to transfer *.log from all directories and subdirectories of /var.
Directories have to be created remotely only if files match
That last
On Sun, 2007-11-11 at 12:47 -0800, Max Kipness wrote:
Is there anyway on a dry-run to actually see per file how many bytes are to
be transferred? On a normal run I use --log-format=/%f/%l/%b/%i which shows
the total file size and the actual bytes transferred.
Also, during a dry-run, is
On Fri, 2007-11-09 at 12:33 -0400, Jon wrote:
I'm so confused as to what keeps happening to my subject. I started
this thread as something like Number of files transferred is wrong
and the two replies I've received so far have totally different
subjects.
In the copy of your message that I
On Fri, 2007-11-09 at 11:29 -0400, Jon wrote:
One piece of information that I forgot to
mention in my original post is that the second rsync takes about 3
seconds. There are no files transferred on the second rsync yet the
293 are being reported.
If the files were actually being transferred
On Thu, 2007-11-08 at 23:55 +0100, Mojca Miklavec wrote:
if I try to rsync (copy) windows
binaries to a windows machine, I experience permission problems when
trying to run them.
You might have more luck asking on the cwRsync forum:
On Fri, 2007-11-09 at 11:11 -0400, Jon wrote:
We can see from the literal data and the matched data from each
session that the first session transferred a large amount of data (as
expected for the initial rsync) and the second session transferred
nothing but overhead (again, as to be expected
On Thu, 2007-11-08 at 12:30 +0100, Janusz Jurski wrote:
I have just noticed an undesired behavior when using rsync when disk
quota is exceeded.
1) I normally execute two following commands to synchronize folders
between a local host and a remote host:
rsync -aCPvu --existing dir1 [EMAIL
On Thu, 2007-11-08 at 18:36 +0100, Janusz Jurski wrote:
But it seems to me that this is against the description of the partial
option in rsync manual.
In my opinion, the partially
transferred file shall be kept for future reuse and shall not overwrite
the destination file.
Also, the
On Wed, 2007-11-07 at 09:13 -0500, Charles Perreault wrote:
For what I read about that lax patch, using it is risky. In fact
that's not what I want at all, I want the content to be checked using
block checksums and the delta-transfer algorithm if the detection did
a mistake, like the
On Wed, 2007-11-07 at 00:08 -0500, [EMAIL PROTECTED] wrote:
Then how about this: If your patch winds up in rsync, it requires a
patch to the manpage entry for -n that says, essentially, You can't
trust the actual information emitted when running with -n to match
what gets emitted if you
On Wed, 2007-11-07 at 06:54 -0800, Wayne Davison wrote:
On Tue, Nov 06, 2007 at 10:22:56PM -0500, [EMAIL PROTECTED] wrote:
I worry about those trying to write things that parse rsync's output;
I had a similar reaction, and will not be eliminating the speedup from
the output. If there is
On Thu, 2007-11-08 at 00:06 +, Wayne Davison committed:
[...] and the speedup value is equivalent to a run where no file
transfers are needed.
Do you not accept that the speedup printed on a dry run is meaningless?
Come on. My bank's online bill payment system knows better than to
On Mon, 2007-11-05 at 21:24 -0800, Wayne Davison wrote:
On Tue, Nov 06, 2007 at 12:04:19AM -0500, Matt McCutchen wrote:
This patch adds an option --tr=BAD/GOOD to transliterate filenames.
Both sides need identical file names in the list when sorting, otherwise
a name could sort
Jeff,
Wayne has cleaned up my patch a bit. The new version is at:
http://cvs.samba.org/cgi-bin/cvsweb/rsync/patches/transliterate.diff?rev=1.1content-type=text/x-cvsweb-markup
Matt
On Tue, 2007-11-06 at 08:29 -0500, Matt McCutchen wrote:
On Mon, 2007-11-05 at 21:24 -0800, Wayne Davison wrote
On Tue, 2007-11-06 at 22:22 -0500, [EMAIL PROTECTED] wrote:
I worry about those trying to write things that parse rsync's output;
if -n changes the output format, such things will have to be tested on
live data.
No, just run rsync's output through a sed script that adds the desired
speedup to
On Tue, 2007-11-06 at 22:10 -0500, Charles Perreault wrote:
now input the following to test moving into a new folder :
$ mkdir src/dir1
$ mv src/file2 src/dir1/
$ rsync --detect-renamed -avz --delete src/ dest/
building file list ... done
deleting file2
./
dir1/
dir1/file2
sent 24031
On a dry run, rsync displays a speedup value calculated from the total
size of the source file data and the amount of data sent over the
connection, but this value is meaningless and grossly misleading because
the file data is not sent over the connection. Example:
[EMAIL PROTECTED] test]$ rsync
On Tue, 2007-10-30 at 21:25 -0400, Charles Perreault wrote:
I heard recently about the detect-renamed patch for rsync. I was about
to code something similar, I need it badly, but decided to give the
patch a try first. It seems to work well but it's rename detection
scheme seems to be
On Tue, 2007-10-30 at 10:07 -0500, Jeff Weber wrote:
Is there a solution to rsync Linux file paths with restricted NTFS
characters, to NTFS? Perhaps there exists a solution to remap. say,
Linux path ; [colon] to an alternate character ! [exclamation mark] on
NTFS ?
Rsync currently does not
On Sat, 2007-11-03 at 18:14 +, 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
I observed the following about --relative:
1. From the user's perspective, its only effect is to change the suffix
of a source argument path that is included in file-list paths. The
suffix starts after the first ./ with --relative or the last / without
it; if the marker is not present, the
It would be nice if rsync offered a way to specify individual dirlinks
to keep without keeping all dirlinks. (Unison can do this.) For
example, consider the following command:
rsync -a --relative src/./ dest/
If rsync refrained from trimming a trailing /. off of source arguments
(at least as
On Sun, 2007-11-04 at 13:34 -0800, Wayne Davison wrote:
On Sun, Nov 04, 2007 at 03:57:11PM -0500, Matt McCutchen wrote:
If rsync refrained from trimming a trailing /. off of source arguments
(at least as an option), one could keep a dirlink by passing it as an
additional source argument
On Sun, 2007-11-04 at 13:50 -0800, Jesse Thompson wrote:
What would be the closest approximation to something like this?
# rsync -r --just-nuke-the-target remote::volume/directory
Is it something that can be done with rsync?
Yes, but it is a bit awkward because rsync considers deletion of
On Tue, 2007-10-30 at 17:20 -0400, Matt McCutchen wrote:
I noticed that rsync is happy to hard-link a device node from a
--link-dest dir even if its mtime differs from that of the source device
node and --times is given. Is this behavior expected? It seems to
break the rule that a difference
On Thu, 2007-11-01 at 11:30 +0100, Paul Slootman wrote:
If so, is there an easy way to configure rsync to stop execution at a
specific time?
No...
Well, there is the patch patches/time-limit.diff in the rsync source
tree that adds options to make rsync stop at a certain time or after a
On Thu, 2007-11-01 at 13:42 -0700, Noam Birnbaum wrote:
Matt, what kind of signal would my script have to send to make rsync
clean up and quit?
SIGINT or SIGTERM should work.
Matt
--
To unsubscribe or change options: https://lists.samba.org/mailman/listinfo/rsync
Before posting, read:
On Thu, 2007-11-01 at 10:35 +1000, Franc Carter wrote:
If am rsyncing a file and I have the the following sequence of events
happen in
the same second
1. rsync starts
2. rsync sends some chunk of data to the other end
3 a local process modifies the chunk that has just been sent
On Tue, 2007-10-30 at 08:50 -0400, [EMAIL PROTECTED] wrote:
[...] I believe leaving off --keep-dirlinks
will not cause any problems, as the symlinks that point to directories on
the primary drive will still be intact on the backup drive, and can be
restored as is on a restore, correct? We
I noticed that rsync is happy to hard-link a device node from a
--link-dest dir even if its mtime differs from that of the source device
node and --times is given. Is this behavior expected? It seems to
break the rule that a difference in preserved attributes disqualifies a
hard link.
To see
I have discovered a few oddities with --relative in the latest
development rsync (from git, yay!):
#1. Junk in the middle of a source argument leads to duplicate entries
in the file list:
$ mkdir src src/D
$ rsync-dev -ni -rR ././src/.//.//.//.//.//.//.//./D/ dest/
cd+ src/
cd+
Wayne,
The man page description of --perms suggests defining -s as a popt
alias, but I think this is no longer a good idea now that -s means
--protect-args .
Matt
--
To unsubscribe or change options: https://lists.samba.org/mailman/listinfo/rsync
Before posting, read:
Wayne,
The rsync Web site at http://rsync.samba.org/ still claims that rsync is
available under the GPL version 2. Now that a bunch of people are
testing prereleases of rsync 3.0.0, you might want to update the site so
that they don't assume they can distribute rsync 3.0.0 under the GPL v2.
On Mon, 2007-10-29 at 13:15 -0400, [EMAIL PROTECTED] wrote:
If I have a backup script that does the following:
(latest 2.6.9 rsync)
rsync --archive --hard-links --force --ignore-errors --numeric-ids
--keep-dirlinks --delete / /backup
I've found that if there is a symlink in place that
On Mon, 2007-10-29 at 19:44 +0200, Pournaris Charalampos wrote:
If I have a directory tree in the source machine like the following:
192.168.1.1 = /raid/system/mainfolder/folder1/subfolder/myfile.txt
and the target machine directory tree looks like:
192.168.1.2 = /raid/system/mainfolder/
Wayne,
The setting of updating_basis on line 403 of receiver.c, outside the
while loop, looks wrong to me: one file with a fuzzy or alternate basis
causes updating_basis to be set to 0, preventing the writing of
subsequent files from being optimized. Shouldn't updating_basis be
reset each time
On Sat, 2007-10-27 at 23:58 -0700, Wayne Davison wrote:
Yeah, it wasn't getting set right. I've moved the initialization to a
spot where we can be 100% sure that it is getting set right. Thanks!
Shouldn't updating_basis be enabled for FNAMECMP_BACKUP as well as
FNAMECMP_FNAME?
Matt
--
To
Wayne,
Around line 637 of receiver.c, the receiver creates any missing parent
directories of the destination file. This looks unnecessary because the
generator ensured at line 1206 of generator.c that the parent
directories existed (or encountered an error creating them that is
unlikely to have
On Sun, 2007-10-28 at 12:41 -0700, Wayne Davison wrote:
On Sun, Oct 28, 2007 at 11:02:35AM -0400, Matt McCutchen wrote:
Shouldn't updating_basis be enabled for FNAMECMP_BACKUP as well as
FNAMECMP_FNAME?
No, we use the backup file as the basis file when --inplace is combined
with --backup
On Fri, 2007-10-26 at 22:22 -0700, Wayne Davison wrote:
I've just released rsync 3.0.0pre4, the second pre-release version
for the upcoming 3.0.0 release.
I have built RPMs of rsync 3.0.0pre4:
http://mattmccutchen.net/rsync/#rsync-packages
Matt
--
To unsubscribe or change options:
On Thu, 2007-10-25 at 18:55 -0600, Rob Bosch wrote:
I received the following error on the client when testing the pre2
release.
4 [main] rsync 8728 _cygtls::handle_exceptions: Exception:
STATUS_ACCESS_VIOLATION
This might be the same crash that Erik Jan Tromp reported here:
Wayne,
I would like to import the entire rsync CVS repository into git for my
own use. I can do this by fetching revisions one by one from the
pserver, but it's abominably slow and probably bogs down the server
unacceptably. Is there somewhere I can download a snapshot of the
repository (which
On 10/17/07, Alexander Skwar [EMAIL PROTECTED] wrote:
/opt/csw/bin/rsync --port=55873 -avPi winds06.win.ch.da.rtr::racebeta/xml \
winds06.win.ch.da.rtr::racebeta/xrfsharedresource \
/opt/apps/Teamcenter/Production/racebeta
b) Why does rsync copy files to this directory in the first place?
On 10/15/07, Aaron Digulla [EMAIL PROTECTED] wrote:
Can you please modify the backup options to work together with
--remove-source-files so I'm able to create a reliable move between
hosts script?
The patch patches/source-backup.diff in the source tree adds an
option --source-backup to do
Please CC the list so people other than me can help you and so your
messages will be available to future users.
On 10/15/07, Mario Domgörgen [EMAIL PROTECTED] wrote:
No, i don't run the client side command myself. The backup should start
from the server, so i use the the second command to
On 10/13/07, Alan Cheers [EMAIL PROTECTED] wrote:
If you had multiple people making rsync backups over ssh wouldn't it be
preferred to use the single-use daemons from a security standpoint? If
multiple people use this method I would want to limit the chance of somebody
being able to grab
On 10/15/07, Aaron Digulla [EMAIL PROTECTED] wrote:
Thanks for the input. If this wasn't for a production system, I'd do
that :-) Why don't you apply the patch the release version?
Because the patch is a quick hack to serve a niche need, so the
benefit of saving people who need source backups a
On 10/15/07, Aaron Digulla [EMAIL PROTECTED] wrote:
Thanks. I'll try to convince my bosses to see this as payment for
using rsync :-) I just hope I can find a simple way to build rsync on
Windows ... I guess I'll try with Cygwin since I already have that
installed and I could build GhostPCL
On 10/15/07, Wayne Davison [EMAIL PROTECTED] wrote:
Is there a system call that allows their permissions to be changed
after they've been created? (Since lchmod is lacking.)
I don't think so, but as Wesley hinted, one can effectively change a
symlink's permissions by deleting it, setting the
On 10/15/07, Erik Jan Tromp [EMAIL PROTECTED] wrote:
# The second error
Invalid file index: -101 (-1 - 0) with iflags 0 [receiver]
rsync error: protocol incompatibility (code 2) at rsync.c(273)
[receiver=3.0.0pre2]
rsync: connection unexpectedly closed (21 bytes received so far) [generator]
On 10/13/07, Wayne Davison [EMAIL PROTECTED] committed:
Added Files:
detect-renamed-lax.diff
Log Message:
My version of Matt's --trust-rename patch.
The option --detect-moved should be named --detect-moved-lax because
it contains the lax behavior. --detect-moved would mean use a file
On 10/16/07, Wayne Davison [EMAIL PROTECTED] wrote:
It also allows for
future expansion in certain situations -- e.g. I can imagine making a
future version of --prune-empty-dirs and/or --delay-updates compatible
with inc-recursion, and this will allow a more modern rsync to try to
tell a
On 10/16/07, Wayne Davison [EMAIL PROTECTED] wrote:
Yeah, I agree that it is better for the client to explicitly tell the
server what is going on (and allows a batch file to indicate what is
happening too).
Now you could revert the unconditional sending of --detect-renamed in
On 10/16/07, Matt McCutchen [EMAIL PROTECTED] wrote:
(That's why I said negotiate.)
One more thing I want to point out in case you haven't already thought
of it. Once two-way negotiation is in place, each side should refuse
incremental recursion only if it can't fulfill its *own* duties under
destination
file without verifying that its data matches that of the source file.
This is risky but it is what Greg [EMAIL PROTECTED] wanted:
http://lists.samba.org/archive/rsync/2007-October/018827.html
This patch is EXPERIMENTAL, though it did work correctly in my single test.
-- Matt McCutchen
Wayne,
The detect-renamed.diff in the current CVS rsync appears to be very
badly broken. I have fixed it and made some other improvements:
Crash fixes:
- Move misplaced the_fattr_list initialization hunk back to recv_file_list
- Send --detect-renamed to the sender so it knows to disable
. I didn't even know that it was available in that tarball. I
have really no experience in making or modifying rpm's. New stuff to learn!
Frank.
From: [EMAIL PROTECTED] on behalf of Matt McCutchen
Sent: Thu 10/11/2007 5:58 PM
To: Frank Thomas
Cc: rsync
On 10/12/07, Alexandros Papadopoulos [EMAIL PROTECTED] wrote:
With that in mind, I would go for one daemon on machine A, and the two
other machines using simple scripted rsync commands to exchange data
with the daemon.
Having the other machines connect to A via ssh may be easier than
setting
in my light
testing.
FIXME: If a run with --trust-rename stages a different-basename destination
file and then gets interrupted, a subsequent run with --trust-move trusts
the staged file.
-- Matt McCutchen [EMAIL PROTECTED]
--- old/generator.c
+++ new/generator.c
@@ -80,6 +80,7 @@ extern int
On 10/12/07, Frank Thomas [EMAIL PROTECTED] wrote:
Thank you for telling me of it's issues. When the patch approaches testing,
please contact me and I can setup a test environment to test transfers in the
Gig's.
I have fixed the patch and Wayne has committed my fixes to the CVS.
You may test
On 10/11/07, Frank Thomas [EMAIL PROTECTED] wrote:
Thanks Matt for your reply. What my problem is, I didn't install rsync
from source, but through a rpm package. I wonder if it is possible to
apply the patch and re-create the rpm, to minimize the work involved.
Yes. Obtain the rsync source
901 - 1000 of 1581 matches
Mail list logo
