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 th
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 th
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 ge
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
Here's an improved version of an old patch that I submitted. It
improves the -vvv output when using --exclude and --include options:
Index: rsync/exclude.c
--- rsync/exclude.c 23 Jan 2002 04:57:18 - 1.39
+++ rsync/exclude.c 30 Jan 2002 18:35:46 -
@@ -201,9 +201,11 @@
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 an
On Thu, 31 Jan 2002, Dave Dykstra wrote:
> It's up to Martin to decide, but I'm sorry to tell you that I'm opposed to
> a --move-files option. I think that if somebody wants to do that they
> should do it with an external program after rsync returns a clean exit
> code. It seems to me that it go
On Thu, 31 Jan 2002, Dave Dykstra wrote:
> Ouch, is that another byte for every file? Are there no bits free in
> the "flags" field already in file_struct?
Yes, it is an extra byte per file. An earlier patch of mine did use
bits in the existing flag word in the current per-file structure,
but s
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,
thoug
On Thu, 31 Jan 2002, Wayne Davison wrote:
> As for the move-files option, I was thinking that I could write a perl
> script that would parse the output of rsync -v and delete files that
> were successfully transferred by rsync when they show up in the verbose
> output.
I'v
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 th
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
variabl
On Thu, 7 Feb 2002, Martin Pool wrote:
> A general-purpose RSYNC_OPTS variable would be more tasteful. I think
> popt makes supporting this fairly straightforward.
That's a nice idea. One area we'll want to be careful of is how the two
options interact.
For instance, we want to support old scr
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, wh
On Sun, 10 Feb 2002, Nishikant Kapoor wrote:
> I am trying to fetch a single dir using the following command but all I
> get is a empty dir:
>
> rsync -av www.myServer.com::myStuff --include=myDir --exclude=* .
Includes are tricky that way -- you told it to just include the
directory, but you did
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 exc
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..
---8<--8<--8<--
Since rsync can now be configured with a different default remote shell
than "rsh", I think the docs should be updated a bit. Anyone object to
these changes?
(Note that I also fixed the misstatement that ssh prefers blocking IO.)
..wayne..
---8<--8<--8<--8<---cut here--->8-->8-
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 tran
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 d
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 run
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 cl
On Thu, 9 May 2002, Dave Dykstra wrote:
> Maybe I'm dense, but I don't see how that's any different from turning
> on a flag (with the opposite meaning) at the end.
The reason this makes a difference is that not all the files get into
that code. Any files that are identical just get skipped over
On Thu, 9 May 2002, Dave Dykstra wrote:
> I would say it's definitely too risky for 2.5.6.
What would you say to adding a (simple) loop to the fnmatch() code that
would cause unanchored things like "foo/*/bar" to not be bound to the
start of the filename? This would make it work in an equivalent
On Thu, 9 May 2002, Wayne Davison wrote:
> What would you say to adding a (simple) loop to the fnmatch() code that
Just to clarify (since the above is poorly worded) -- I meant adding the
loop to the rsync code that calls fnmatch(), not trying to modify the
fnmatch() code directly.
..wa
On Thu, 9 May 2002, Dave Dykstra wrote:
> How many times would you have to call fnmatch for every file?
We'd call fnmatch() an extra time for every slash in the path. However,
the performance hit of this new loop on the pattern "foo/*" would be the
same as using the two patterns "/**/foo/*" & "/
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-sla
On Fri, 10 May 2002, terrell Larson wrote:
> If rsync is directed to copy a directory tree into another machine and
> the target directory does not exist then rsync will not create the
> required path
Dave Dykstra just recently responded to another user that this is the
intended behavior of rsync
On Fri, 10 May 2002, jw schultz wrote:
> Also the example is an odd one.
It doesn't seem odd to me since the -l option is the one that I've used
most in ssh (when I don't use the config file to avoid all options).
The important part of the example is showing how it's quoted, so what's
in it could
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 08:31
On Mon, 13 May 2002, Peter Møller Neergaard wrote:
> types:/<3>tmp/wwwreports-dont-edit > echo *.html
> [...lots of files with colons in them...]
Rsync treats a colon on the commandline as a separator between a machine
name and the filename, so you can't use *.html if it expands to one or
more na
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:
foo/
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 c
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 t
On Fri, 17 May 2002, Wayne Davison wrote:
> so feel free to tell me exactly where I've missed the boat.
[Replying to myself... hmmm...]
In my description of the _new_ protocol, my references to a generator
process are not really accurate. The current generator process is
forked off a
On Fri, 24 May 2002, Mike Rogers wrote:
> RSYNC maybe once a day or so will just hang and sit there...
You don't mention what version of rsync you're using. Version 2.4.6
would often hang when the -v option was used, so if you're using that,
you'd do well to upgrade.
> strace attached to the pr
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 u
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 ago
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 c
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 change
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:
http://ww
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 i
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
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
For the small number of people who are checking this out, I released
version 0.05 a couple days ago (and only mentioned it on my new-protocol
web page) followed today by 0.06. Some highlights of the two releases:
- We handle symlinks now in our recursive synchronization mode.
- Directory scanni
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 o
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 beg
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 po
I've released the next version of my rZync test app. You can find a
link to it here:
http://www.clari.net/~wayne/new-protocol.html
You should also snag the referenced librsync source, as some important
bugfixes in librsync are needed to compile rzync.
For those that don't know, rZync is my
Martin Pool <[EMAIL PROTECTED]> wrote:
> I've put a cleaned-up version of my design notes up here
> http://samba.org/~mbp/superlifter/design-notes.html
I'll start with some feedback on your rzync comments:
Re: rzync's name: I currently consider the rZync to be a test app to
allow me (and an
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 instea
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, e
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 au
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 o
> 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 neede
On Wed, 31 Jul 2002, Robert Weber wrote:
> On the subject of needed patches, I just recently completed a patch for
> librsync that fixed the mdfour code to have uint_64 or 2 uint_32's for
> size. Without this, the checksums on files >512Megs are incorrect.
In order to interoperate with older ver
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 pat
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'
I just looked over your latest changes and checked in a few minor fixes
that I saw:
- In client_addr() we now avoid calling getnameinfo() if we've already
setup the addr_buf (in the am_server side).
- I moved some structures in client_name() so that they remain in scope
the entire time that
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 previou
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 s
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 u
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 gav
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.sam
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, 5 Sep 2002, Quang Tran Hong wrote:
> NormalFile.
> 23 (100%)
> rename .NormalFile..idNZdb -> NormalFile. : File exists
You'll note that in these messages that the dot has not been lost, so
it's not rsync's doing that is causing this problem. It looks to be a
deficiency in your OS. Are y
On Tue, 17 Sep 2002, Bjorn Graabek wrote:
> and here are (currently) the contents of my exclude.txt file:
>
> ---
> + /my documents*
> + /favorites*
> + /cookies*
> + /local settings/application data/microsoft/outlook/outlook.pst
> - /*
> ---
I think the first problem is that you aren't using th
On Tue, 1 Oct 2002, Nick Papadonis wrote:
> [In 2.5.5] --delete-after [...] must be used with --delete to work.
Unfortunately. In the current CVS version, however, --delete-after now
implies --delete and the man page mentions this fact. So, this will
work more logically whenever 2.5.6 gets rele
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 (
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 old
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 fil
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 t
On Tue, Nov 12, 2002 at 03:27:03PM +0200, Mozzi wrote:
> [root@ais-mail01 root]# time rsync -pogrve ssh /var/spool/mail
> [EMAIL PROTECTED]:/var/spool/mail/
FYI, this command puts the "mail" dir inside /var/spool/mail on the
destination. You should add a trailing slash to the source path to
avoi
On Tue, Nov 12, 2002 at 04:32:31PM +0100, [EMAIL PROTECTED] wrote:
> I'd call it a bug.
No, it's not a bug. It's the heart of the rsync algorithm at work.
Rsync trades CPU and local file I/O for network I/O in order to reduce
the amount of data that is transferred over the network. Your diagnosi
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 m
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 inclusio
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 Fri, Dec 06, 2002 at 11:53:08AM -0800, Sander van Zoest wrote:
> I would like to be able to use rsync to mirror some directories, but
> to explicitly *not* override any files that already exist on the other
> side.
I believe you're looking for the --ignore-existing option. I'm not sure
when it
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: http://lists.samba.org/mailman/li
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
- /va
On Sat, Jan 04, 2003 at 12:40:05PM -0800, jw schultz wrote:
> One specifying subpaths and the other for those having a shared
> prefix.
I don't see why this is needed. For instance, your example of a shared
prefix:
> find srcdir | myfilter | rsync --file-list - srcdir destloc
would be eas
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 op
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,
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
trai
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 trans
1 - 100 of 2912 matches
Mail list logo
