On Mon, Oct 30, 2000 at 09:03:31PM -0500, Paul D. Smith wrote:
> Just a directory named /progs (/proc, /dev, /mnt). Man page sez:
>o if the pattern ends with a / then it will only
> match a directory, not a file, link or device.
Yeah, that's what it says. This i
%% [EMAIL PROTECTED] writes:
j> rsync -ca --delete --exclude "/proc/" --exclude "/dev/" --exclude
j> "/mnt/" --exclude "/progs/" [EMAIL PROTECTED]::gates /data/gates
j> To clarify, would the above example exclude /progs and also
j> /data/progs/ or just the /progs directory from the root
Having a bit of trouble understanding the "exclude" option for the rsyncd
daemon
Does my example below exclude the /proc /dev /mnt and /progs from the root
directory "/"
or would it also exclude a directory of the same name if it is within the
tree I want to back up?
rsync -ca --delete --exclu
On 15 Sep 2000, Dave Dykstra <[EMAIL PROTECTED]> wrote:
> An important point you have missed: the -e option is ignored when
> you're connecting to an rsync daemon (that is, either "rsync://" or
> "::" syntax). Ssh cannot be used in combination with it. Rsync
> really ought to be changed to repo
On 30 Oct 2000, Dan Phoenix <[EMAIL PROTECTED]> wrote:
> I am going to ask again...digest version of this list exist or
> not?
Yes; just go to
http://lists.samba.org/
choose rsync, enter your email address or choose it from the list, and
change the digest option.
If you need any other
On 30 Oct 2000, "Mark W. Eichin" <[EMAIL PROTECTED]> wrote:
> Instead of making up some hashing key-generation method, please look
> at RFC2104 "HMAC" (and the six or seven followup rfc's on specific
> instantiations.)
>
> Also, for rsync, I don't see why you'd particularly want a stream
> cipher
I am going to ask again...digest version of this list exist or not?
---
Dan
+---+
| - Daniel Phoenix Mail to:[EMAIL PROTECTED]| |
| | / ___ |
On 30 Oct 2000, "Paul D. Smith" <[EMAIL PROTECTED]> wrote:
> My arguments to rsync were causing the remote tree to be
> reconstructed one level down from where I wanted it to go, which
> obviously caused all the files to be sent over.
This is a little confusing, though it's necessary that we all
Hi folks; thanks for the responses.
I figured out the problem. My arguments to rsync were causing the
remote tree to be reconstructed one level down from where I wanted it to
go, which obviously caused all the files to be sent over. Because I was
using -n just to see what would happen, so no ac
I agree with Martin Pool's diagnosis about --times, or --archive
which includes it along with many other options. If some of the
systems can't represent file mod times to the same resolution, the
--modify-window option may be helpful as well.
If you don't care to update timestamps, you can use --
Instead of making up some hashing key-generation method, please look
at RFC2104 "HMAC" (and the six or seven followup rfc's on specific
instantiations.)
Also, for rsync, I don't see why you'd particularly want a stream
cipher (it isn't interactive, you have "large" packets to work with)
and I mig
While doing some testing I noticed that you can't set the
blocksize to 700 on large files in rsync-2.4.6. I have attached
a patch that adds a variable that is set when the blocksize is
specified rather that just testing whether it is not equal to
the default setting.
Brian
--
"...and that's
12 matches
Mail list logo
