On Fri, 13 Apr 2001, Dave Dykstra wrote:
Although I've heard the suggestion before, my first reaction is that it
would seem to be counter to the main purpose of rsync which is to make
files identical in two places; that is, there is no need for the rsync
rolling checksum algorithm if the file
On Tue, 1 May 2001, Jeff Ross wrote:
rsync -aqR -exclude-from=/root/exclude.txt \
-e ssh * redhat62:/backup/rsync/firewall
Here's a W.A.G.: Is the exclude.txt file in DOS format (with CR+LF
line endings)?
..wayne..
On Fri, 4 May 2001, Benoit Langevin wrote:
I am new using rsync, and it got some advantage, but do you know if I
do the equivalent of a move with rsync. I have a case where I need to
delete the remote after retrieving it.
I had the same need, so I wrote a patch for rsync. It turned out to
On Fri, 11 May 2001, Dave Dykstra wrote:
The optimization bypassed the normal recursive traversal of all the
files and directly opened the included files and sent the list over.
There's an alternative to this optimization: if we could read the
source files from a file (or stdin), we could use
Pardon my persistence, but I'm curious about what the decision was for
the --move-files option. I just finished an exchange with the openssh
folks where I tried to get scp to have both a move-files option and an
option to use a temp file to put the file whole finished into its
destination.
I'm checking into the innards of rsync in order to try to figure out the
best way to add a proper move-files option, and I think I discovered a
potential hang when sending large numbers of files between systems. If
I understand this correctly from my preliminary reading of the code, the
I've been doing some testing where I trigger the rsync hang I talked
about in my previous email (where the redo pipe to the generator process
fills up and causes the receiver to deadlock). This bug is easy to
trigger on a local-to-local rsync copy if I change receiver.c to retry
every file
I think I've tracked down another hang in rsync 2.4.6. This one appears
to be caused by the sender process finishing up all its work and going
into a pid-reading loop before it finishes reading all the error stream
coming in from the generator process -- if this data is large enough,
the
I've worked up a new --move-files option that doesn't delete the files
on the sending side until the receiver is known to have successfully
written the data. I didn't want to implement a delete-pass at the end
of the send since I wanted the files to get deleted as we go. However,
because of the
Remi Laporte wrote:
Rsync 2.4.6 -v option is bugged and cause hangs of the transfers, so if
you have such problem, first think to remove the -v.
On Thu, 7 Jun 2001, John E. Mayorga wrote:
Can anyone else confirm this?
My recently posted anti-hang patch should hopefully fix this for you.
On Sat, 9 Jun 2001, Christian Gilmore wrote:
As an example, user foo has an account on the local and remote system. He
wishes to use rsync to synchronize files that are read-only on the source.
Rsync already handles this case for you automatically. It also handles
the case where you are
On Wed, 13 Jun 2001, Jurgen Botz wrote:
I'm seeing the following bizarre behavior...
- rsync -av from one local fs to another local fs (local disk on both)
- rsync gets to very near completion then hangs indefinitely
- attach strace to rsync process doing the 'copy from' and
it
The CVS version of rsync outputs an error on exit after listing the
modules from an rsync daemon (running rsync host::). The following
patch fixes this. (If you haven't applied my nohang patch, you'll see
an offset for this patch hunk.)
..wayne..
---8--8--8--8---cut
On Thu, 14 Jun 2001, Martin Pool wrote:
I'm slightly concerned that this may cause some other failure modes to
falsely cause the client to return 0.
I was thinking about this myself. The code sets eof_error = 0 for any
user of read_line(), and (judging from my quick inspection) this doesn't
On Thu, 14 Jun 2001, Wayne Davison wrote:
Here's a patch.
I forgot to mention that you should run make proto after applying that
patch.
..wayne..
On Mon, 18 Jun 2001, Jeremy Sanders wrote:
I'm getting numerous rsync (v2.4.6) problems under Linux 2.4.2 (RedHat
7.1) or stock 2.4.4 on several machines. rsync often hangs copying files
from NFS or local disks to local disks. Strangely the problem is fixed by
stracing one of the three rsync
On Mon, 25 Jun 2001, Dave Dykstra wrote:
On Fri, Jun 22, 2001 at 05:26:52PM -0700, Wayne Davison wrote:
I think a better method would be for rsync to have a default blocking
setting for the default remote shell (perhaps configurable along with
what the remote shell is), and then let
I was wondering if the protocol should be updated to avoid ever
assuming that an EOF on the socket was OK. The only case I know of
where this allowed is when we're listing modules from an rsync server.
If we modified the protocol to have the daemon rsync send an EOF token
(such as @RSYND: EOF)
On Mon, 25 Jun 2001, Andrew Tridgell wrote:
I've applied your simple nohang patch.
Cool. That's the one that affects the most people.
Instead we need a way of reproducing the bug and see if we can find a
solution without a buffer.
You can minimize the buffer usage by applying my move-files
On Mon, 25 Jun 2001, Andrew Tridgell wrote:
see if we can find a solution without a buffer.
Here's a solution with a non-growing buffer. This code keeps the
receiver-generator pipe clear by reading the ints and setting redo
flags in a character array (of flist-count elements). I'm avoiding
On Tue, 26 Jun 2001, Wayne Davison wrote:
Since read_int() is a fairly high-level call, I had to manually ensure
that a flush doesn't happen and to ensure that reading the redo_fd
doesn't try to read the io_error_fd (both to avoid nested read
attempts on the redo_fd).
In case you're
On Wed, 27 Jun 2001, Martin Pool wrote:
This is getting disturbingly complex. I realize the problem is
complex too, so this is no slur on Wayne's coding. My gut reaction is
that if we start adding this then the program's behaviour will become
even more baroque.
We certainly do need to be
I noticed that if the protocol fails in such a way that the generator
cannot write down the pipe to the sender, the error message that it
attempts to send (down the same pipe) causes an infinite recursion, and
the program core dumps when the stack overflows. The following patch to
log.c causes
On Tue, 10 Jul 2001, Steve Ladendorf wrote:
Is there something I'm doing wrong? What can I do to prevent rsync from
hanging all the time??
If you avoid using -v, that can help rsync not to hang. However, a
better fix is to apply this patch:
On Tue, 26 Jun 2001, Martin Pool wrote:
On 25 Jun 2001, Wayne Davison [EMAIL PROTECTED] wrote:
I was wondering if the protocol should be updated to avoid ever
assuming that an EOF on the socket was OK. The only case I know of
where this allowed is when we're listing modules from an rsync
On Mon, 23 Jul 2001, Perry Hoekstra wrote:
why does devel/test.html show up as an add_exclude?
That's because all excludes and includes go through the same function --
an include just has the include flag turned on. The following patch
causes the verbose output to mention the include-flag
On 12 Sep 2001, Michelene Chon [EMAIL PROTECTED] wrote:
We are using rsync and have noticed that it fails to copy hidden
directories.
My guess is that you're using a wildcard and your shell isn't expanding
that wildcard to include dot dirs. For instance:
rsync -av /home/user/*
One thing you could try would be to setup a port-forwarding ssh for port
873 and run an rsync daemon setup. The daemon mode does not use rsh as
you thought: it uses its own (unencrypted without external help)
sockets connections.
..wayne..
On Tue, 13 Nov 2001, Thomas Schweikle wrote:
I am calling rsync using
rsync -avz --include-from=include --exclude-from=exclude
ftp3.sourceforge.net::/netbsd/iso iso/
Looks like you didn't copy that command exactly, because rsync would
fail with a syntax error due to the '/' before the
On Wed, 10 Oct 2001, Andre Pang wrote:
ssh is your problem
I believe Hans said that he only uses ssh to startup the samba-using
process going, and then transfers all files locally with rsync. So,
the problem is that samba is doing all the data transfer over the
network instead of rsync.
So
I'd like to revisit the topic of moving files from system to system
using rsync. I've just updated my patch from its 2.5.0 version to
2.5.1, and I'm curious what people think about getting it integrated
into rsync.
The patch comes in two parts. The first eliminates a potential hang
condition
On Wed, 30 Jan 2002, Dave Dykstra wrote:
Martin has put in the below feature in rsync 2.5.2 for using a shell. I've
already had one user complain about it. I think it would be better at the
-vv level.
Yes, I agree that -vv would be better. People use -v primarily to see
what files are
On Wed, 23 Jan 2002, Wayne Davison wrote:
I'd like to revisit the topic of moving files from system to system
using rsync.
I'm sad that nobody wanted to talk about --move-files yet, but maybe
this will help things along. I've adapted the patch files to be based
on the latest CVS source
A while back I argued for adding a --with-rsh=CMD option to configure
and got some general agreement that it would be a good thing (especially
for systems that don't have rsh at all). However, the changes were
never integrated into rsync.
This patch adds the --with-rsh=CMD option to configure
On Fri, 1 Feb 2002, Steve G wrote:
I don't know if this amounts to much, but did you intend to use a
rather than a at line 739 of flist.c?
Fortunately both items in the expression can only have the value of
1 or 0, so the effect is the same as . It looks like a typo to me,
though.
On Wed, 6 Feb 2002, Martin Pool wrote:
OK, I agree --with-rsh should go in, but I think putting magic
characters into it is needlessly confusing. I would feel much better
about a separate configure option to set the default O_NONBLOCK mode.
The complicating factor then becomes: how does the
On Wed, 6 Feb 2002, Dave Dykstra wrote:
Of the proposed alternatives, I like this latter the best, changing
--non-blocking-io to --no-blocking-io.
Cool. I like that one as well. Here's an implementation. This patch
adds the configure option --with(out)-blocking-io and defines a new
variable
On Thu, 7 Feb 2002, Kapoor, Nishikant X wrote:
I have a few clients who prepare some reports and put it in their
outgoing/ directory for me to pick up every morning. Is there a way to
delete those files from their outgoing/ after I fetch them ?
You can use my --move-files patch for this,
On Wed, 13 Feb 2002, Ian Kettleborough wrote:
ie:
/usr/src
or
/usr/src/
One thing that totally tripped me up at first is that you don't include
the whole path if you're not starting the transfer from the root of the
filesystem. For instance:
rsync -av /usr/ foobar:/usr
All your
On Mon, 18 Feb 2002, Martin Pool wrote:
Why the sleep() call?
Also, why close(fd) twice?
+ } else if (pid 0) {
+ rprintf(FERROR, could not create child process: %s\n,
+ strerror(errno));
+ close(fd);
+
Seems to me that the simplest solution is to name the directory
explicitly:
rsync -a --include */ --include *.tif --exclude * /film/jonah /tmp/film
To accomplish the same thing using includes, you could do this:
rsync -a --include /jonah --include /jonah/**/ --include *.tif \
On Tue, 19 Mar 2002, Jeff Field wrote:
rsync -e ssh source-box.x.com:/var/qmail/control/file1 \
source-box.x.com:/var/qmail/control/file2 \
source-box.x.com:/var/qmail/control/file3 \
source-box.x.com:/var/qmail/control/file4 \
/var/qmail/control
You can't have multiple
On Thu, 25 Apr 2002, Dave Dykstra wrote:
I think --delete-after should imply --delete. Would someone like to
work up the simple patch to the code and the man page?
Sure. Here's one (note that the OPT_DELETE_AFTER enum was already
defined for some reason).
..wayne..
In an effort to get my long-desired move-files functionality into rsync,
I have created a version of my patch that runs as an extra pass at the
end of the processing. This results in a simpler set of changes to
rsync.
I still think it would be nice to have incremental deletions during
large
On Sat, 4 May 2002, Manfred Gnaedig wrote:
If i use this
rsync -varpog -e ssh --stats /home/www/web6
217.172.xxx.xxx:/home/www/web6 --password-file=host1.pwd
the Server is asking me too fore Passwort.
Ssh is asking you for the password. However, the --password-file option
(as well as the
On Sat, 4 May 2002, Michael Fischer wrote:
1. If I touched only the corrupted file, so the file times differed,
then rsync did update the destination file.
2. If I used the --checksum flag, then it updated correctly.
But just a plain rsync failed to notice that the files were
On Sat, 4 May 2002, Manfred Gnaedig wrote:
mkdir 217.172.xxx.xxx/home/www/web10 : No such file or directory (1)
You left out the ::. Also, the syntax for server mode is slightly
different -- you need to refer to a module name on the server. So, if
you have an rsync daemon configured and
Here's a resend of an old patch that is intended to avoid an infinite
recursion (ending in a stack overflow) of the rwrite() function getting
an error that calls rwrite(), ad naseum. I've only seen this happen
when one of the sides dies due to a program error -- in that case, the
connection is
On Fri, 10 May 2002, Dave Dykstra wrote:
If you dynamically created a */*/*/foo/* pattern with the number of */
to match the current path it would only have to call fnmatch once.
That's assuming the pattern doesn't contain an interior/trailing **
(which could only use the try-after-each-slash
OK, I just checked in a change that uses some of your suggested text to
remove a bit of the chattiness. I also improved the RSYNC_RSH section
to mention the legality of command-line options. See if you like it
better.
--- rsync.yo2002/05/09 21:44:46 1.99
+++ rsync.yo2002/05/11
On Mon, 13 May 2002, Dave Dykstra wrote:
I suggest you go ahead and code it in the way you
think would be simplest and then we can evaluate it more concretely.
OK. Here's the simple patch. It optimizes the loop away if the pattern
starts with ** (since the loop would be superfluous), but
Here's a more complex version of the wildcard change that attempts to
count slashes in the pattern (if it does not contain ** anywhere) and
to match at the appropriate level.
In trying to think up patterns where this might mess up, the only thing
I thought of was something like this:
Here's an idea which I haven't had a chance to investigate:
Would it be possible to use atexit() to register a call to shutdown()
for cygwin (or a call to a custom function that would call shutdown()
for the appropriate socket fds)? This should allow cgywin's broken
socket code to get properly
On Thu, 16 May 2002, Brad wrote:
The command which is run on the client:
rsync -avt /var/spool/mail StorageServer::email
Did you either startup an rsync --daemon manually on the server or
setup [x]inetd to spawn rsync --daemon when someone connects to the
rsync port? When you use the ::
On Thu, 16 May 2002, Max Bowsher wrote:
That just moves the shutdown call from where you finish with the fd to
where you start using the fd - that's got to be less intuitive.
Being more or less intuitive is not the point. The idea was to have as
little cygwin kludge code as possible. Thus,
On Fri, 17 May 2002, Allen, John L. wrote:
In my humble opinion, this problem with rsync growing a huge memory
footprint when large numbers of files are involved should be #1 on
the list of things to fix.
I have certainly been interested in working on this issue. I think it
might be time to
I found some time in the past week to work on a simple test app that
would hopefully help to answer a few questions that came up recently:
1. Can a single-process generator+receiver work well? (Looks good so far,
but I haven't run any multi-processor timing tests yet.)
2. How easy is it to
On Fri, 7 Jun 2002, Stephane Paltani wrote:
I have 5 million files on one side of the ocean, 10 of which must
be copied to the other side.
This is the sort of problem that would benefit from the rsync_xfer.c
program I'm working on (I mentioned an early version on the list a week
or so
On Tue, 11 Jun 2002, Simison, Matthew wrote:
c:Connection refused
rsh: can't establish connection
Did you used to have an RSYNC_RSH variable in your environment? Perhaps
one that was set to use ssh? You could run echo $RSYNC_RSH on one of
your Unix boxes to see what they're set to use.
I've been having a lot of fun improving my new-protocol testing app.
It's seems to be in pretty good shape (for test code), so I figured I'd
announce another release for those brave souls that may want to help me
in my thinking about a (potential) new rsync protocol. It's a tar.gz
file this time
On 13 Jun 2002, Bill Geddes wrote:
Suggestions on how to proceed would be greatly appreciated.
It is possible that one side of the connection is seg-faulting and
dying. If you ensure that core files are not disabled (check your
ulimit setting), you may find that there is a core file that you
On Thu, 13 Jun 2002, Wayne Davison wrote:
http://www.clari.net/~wayne/rzync.tar.gz
I forgot to mention that I changed the order of the local/remote args
to the 2-arg version of the cd command to be cd LOCAL REMOTE (the
command cd DIR still changes both the local and remote sides
On Mon, 17 Jun 2002, Sandy Ganz wrote:
Any ideas on how to keep rsync from using all the cpu on the webservers? I
Have you tried running rsync under nice? Start it up on the webserver
side with the same command as before, just put nice at the start and
see if that relieves the pressure on
For anyone who'd like to check out the latest release of my rzync [sic]
test release, I've just released a new version. For those that might
not have time to look at the code but could provide some feedback based
on a rough description, I've created the following simple web page:
FYI, I decided to release a new version of my next-generation protocol
test app because I created an optimized transfer mode when files are
being sent whole (it bypasses all calls to librsync). This makes my
rZync test app faster than rsync for sending whole files (rather than
4x slower, like it
On Mon, 24 Jun 2002, J.Strohschnitter wrote:
is it possible to use regular expressions in the exclude-paramter of rsync ?
For example:
rsync --exclude /path/to/*/[Ff][Oo][Ll][Dd][Ee][Rr]
That's still a valid match pattern (and a poor regular expression --
/* would match zero or more slashes
On Mon, 24 Jun 2002, Bernard A Badger wrote:
Just a comment on shell glob usage [...]
Shell globbing is done before the program is invoked, so
the shell globs on --exclude=/path/to/*/[Ff][Oo][Ll][Dd][Ee][Rr], but
unless you have a directory --exclude=, it won't find anything.
Quite so.
On Wed, 26 Jun 2002, Wayne Davison wrote:
There are still unsquashed bugs lurking, so be careful. For instance, I
tried to copy my .mozilla dir, and the huge Cache hierarchy is currently
giving it grief. I'll debug this problem next.
Turned out to be a silly oversight on a realloc of some
On Mon, 8 Jul 2002, Eric Horst wrote:
Not to mention, is it a real long-term goal is to redesign rsync to deal
with large numbers of files by not building the entire file list up front?
That is something that I'm working on with my rZync application. It
implements a new protocol that can
I'm wondering if we shouldn't just remove popt from the rsync source and
just rely on the user to install the popt package on their system prior
to compiling rsync. Configure already uses the installed popt in
preference to the included popt, so it wouldn't be hard to change this
to not have a
On Tue, 23 Jul 2002, g dm wrote:
rsync -a --delete * /data/exp_dir
So, what did I do wrong?
You're sending a list of files, not a directory (since '*' is expanded
by the shell into a list of files). The --delete option only works on
a directory-to-directory transfer, so try using this
On Mon, 22 Jul 2002, Edward Farrar wrote:
Rsync 2.5.5 is producing this error message and a core file when executing the
command /usr/local/bin/rsync -av --delete --force /net/OSCM/OS_ATLAS2/CONFIG/.
/net/OSCM/OS_TITAN1/2.6/CONFIG/. /OS/2.6/CONFIG
building file list ... done
rsync:
On Sun, 21 Jul 2002, jw schultz wrote:
What i am seeing is a Multi-stage pipeline.
This is quite an interesting design idea. Let me comment on a few
things that I've been mulling over since first reading it:
One thing you don't discuss in your data flow is auxiliary data flow.
For instance,
On Thu, 11 Jul 2002, Jos Backus wrote:
http://www.catnook.com/patches/rsync-popt-1.6.4.patch
I went ahead and tested this and then checked it in (since we might as
well include the newest popt if we're going to include popt with rsync).
The configure script had to be regenerated (with
On Tue, 30 Jul 2002, Martin Pool wrote:
The --password-file option only applies to rsync daemon connections,
not ssh.
Perhaps we should make rsync complain about such options that don't make
sense (another example being trying to use -e with a :: hostspec)?
..wayne..
--
To unsubscribe or
On Wed, Jul 31, 2002 at 10:21:49AM +1000, Martin Pool wrote:
There's just one more change I would like to put in, which is partially
rolling back the IPv6 patch so that it uses the old code, unmodified,
if --disable-ipv6 is specified.
There was another patch that I thought was needed with
On Wed, 31 Jul 2002, Dave Dykstra wrote:
The patch that I'd most like to see get in JD Paul's patch for using
SSH and daemon mode together.
I've completed my mods to get this updated to the latest CVS version and
then checked it all in. Since things had changed quite a bit, I applied
the
On Thu, 1 Aug 2002, Dave Dykstra wrote:
I think the way JD did it was the compromise we agreed on: if a userid
is specified only with userid@hostname, it should be used for both
purposes, but if the -e command includes -l it should override the
login userid only.
OK, that makes sense. I'm
On Sun, 4 Aug 2002, Martin Pool wrote:
My first draft was proposing what you might call a fine-grained rpc
system, with operations like list this directory, delete this
file, calculate the checksum of this file. I think Wayne's rzync
system was kind of like that too.
Your previous proposal
On Mon, 12 Aug 2002, Leaw, Chern Jian wrote:
# rsync -avz --include-from=files_included /stor/circuit_design/
mickey.willowglen.com:/stor/circuit_design/
The problem with your command is that it contains include directives but
no exclusions, so nothing limits the default operation of
On Mon, 12 Aug 2002, Nitin Agarwal wrote:
I want to rsync all the dates directories but only the toid
subdirectory.
The easiest thing to do might be to use the -R (--relative) option, like
this:
rsync -avR /abc/dir/*/toid host:/dest/
This will create the /abc/dir/DATE/toid dirs on the
On Tue, 13 Aug 2002, Leaw, Chern Jian wrote:
I tried your suggestion, but did not work. It still copied the entire
filesystem across to the destination machine.
Since you failed to provide the command-line you're using, I can't tell
you exactly why your command failed. For instance, if you
On Wed, 14 Aug 2002, Ivan Kovalev wrote:
rootdir/*/2002-08-01
rootdir/*/*/1-Aug-02
rootdir/*/2002-08/01
As the documentation states, if you use --exclude=*, you need to include
every parent directory on the way down to the directories in question.
So, it's easy to see that the rules you gave
On Wed, 14 Aug 2002, Wayne Davison wrote:
In a combined file, items that begin with + are always taken to be
exclusions
Of course, that should have been inclusions, not exclusions.
..wayne..
--
To unsubscribe or change options: http://lists.samba.org/mailman/listinfo/rsync
Before posting
On Wed, 28 Aug 2002, Ralf Schreiber wrote:
The partially transfered data (with a dot on first position of the filename)
will be renamed after a ctrl-c occurs (on both
OS) or a window-close (cygwin) to the filename of a fully transfered file
(without the dot), which aren't complete !
Yes,
On Thu, Oct 10, 2002 at 10:49:33AM -0400, Bryan K. Wright wrote:
The master copy of /local contains the directory stuff, not
a symbolic link. The problem is, when I rsync /local on the few
machines that have a symbolic link, the link gets nuked and replaced
with a real directory (just
On Thu, Oct 10, 2002 at 04:50:33PM -0400, Bennett Todd wrote:
The rsync opens the target file to read; if some other rsync moves a
new file into place before that, there's no concurrency, this is
pure sequential rsyncs; if it moves the target file into place after
it's been opened, the older
On Wed, Oct 16, 2002 at 01:36:10PM -0500, Sean O'Neill wrote:
The timestamp should match that of the system the data is pulled from right
? Well, it doesn't from time to time. The time stamp sometimes gets
updated as just Oct 16 2002
This is what most unix systems display for a future
On Thu, Oct 24, 2002 at 12:37:34PM -0400, Shelley Waltz wrote:
Why is there a difference in the size of the directories for marshall(and
many others) which makes the distination larger than the source?
The directory listings you provided show that there are hard-linked
files on the source
On Mon, Oct 28, 2002 at 03:12:53PM +0800, Patrick Hsieh wrote:
Since foo has no write permission under /var/www, he cannot rsync
from remote server to the local filesystem because rsync will try to
make temp file and unlink the original file before writing over it. Is
there any solution to
On Tue, Nov 12, 2002 at 11:30:28PM +0100, [EMAIL PROTECTED] wrote:
And why it tries to get 100% CPU even though there's nothing to do ?
What do you mean nothing to do? Rsync is creating the new version of
a changed file which is done both by transferring data over the network
and by copying
On Tue, Nov 19, 2002 at 11:32:06AM -0600, Lori Anderson wrote:
rsync -av /software/testdir/ --exclude='/software/testdir/test.sql'
landser@serv602:/software/testdir/
Inclusions and exclusions are relative to the base of the transfer. Use
a leading '/' if you want to indicate that the
On Mon, Nov 25, 2002 at 09:30:03AM -0500, Jeff Bearer wrote:
But if the file isn't modified, the modified time shouldn't be updated,
By default, rsync uses the time size on the file to determine if it
was updated. Since the source and destination files don't match, rsync
transferrs the file,
On Mon, Dec 09, 2002 at 01:49:40PM +, rsyncuser wrote:
We are interested in finding out whether the wayne-nohang patches can
be applied to 2.4.6.
My older patches for 2.4.6 had got moved aside after they got
incorporated into the main distribution. However, I just put them back
in their
On Mon, Dec 09, 2002 at 04:36:41PM +0100, Markus Lamers wrote:
rsync -auvxz --delete --exclude-from /root/.rsync/home-daily.exc /home
slave:/
I suspect the home-daily.exc file is at fault. What does it contain?
..wayne..
--
To unsubscribe or change options:
On Tue, Dec 10, 2002 at 09:18:06AM -0500, marco wrote:
I even tried this but it include the whole /var/ folder !
I just want /var/lib/zope.
The solution is that after you include something that is too general,
you need to exclude what you don't want. Like this:
/etc
/var
- /*
/var/lib
-
On Sat, Jan 04, 2003 at 05:03:02PM -0800, jw schultz wrote:
that would produce destloc/srcdir/
when you might want a copy of srcdir at destloc instead of
in destloc.
Ah yes, I _was_ missing something. However, I still don't think we need
to clutter rsync with two types of --file-list
On Sun, Jan 05, 2003 at 11:55:22AM -0800, jw schultz wrote:
The first problem is this would flatten things unless you used
relative and forced the user's CWD. That would cause considerable
confusion.
Really? This is exactly how rsync works now with multiple file names on
the command-line, so
On Wed, Jan 08, 2003 at 04:42:58PM -0800, jw schultz wrote:
- RCS,SCCS,CVS,CVS.adm,RCSLOG,cvslog.*,
+ RCS/, SCCS/, CVS/, CVS.adm, RCSLOG, cvslog.*,
Might be worth doing to tighten the patterns.
Yes, I'd agree with that. I looked at the code to confirm that the
trailing slashes would be
On Thu, Jan 09, 2003 at 07:48:50AM -0600, Max Kipness II wrote:
Total file size: 383219712 bytes
Total transferred file size: 383219712 bytes
Literal data: 3143680 bytes
Matched data: 380076032 bytes
The total file size is definitely correct, but what I don't understand
is the transfered
1 - 100 of 6369 matches
Mail list logo
