On Thu, Aug 03, 2006 at 10:22:57AM -0400, Erik Jacobs wrote:
> is there any reason why telling rsync what files you want it to
> INCLUDE doesn't seem to tell it what files to include?
Without -r or -d, rsync completely skips directories (just like it skips
symlinks without -l). Just because a nam
On Thu, Aug 03, 2006 at 03:12:40PM +0200, Paul Slootman wrote:
> Note that the trailing slash *is* needed on the ssh connection, see
> without:
>
> local# rsync --exclude='*' --include='.*' remote:/tmp/test
> Password:
> (nothing)
That's because you excluded the directory "test", which is the f
On Thu, Aug 03, 2006 at 08:16:54AM -0400, Erik Jacobs wrote:
> If I add the recursive option, it works, but I don't want to recurse
> -- I only want to look at the files in this folder...
On a modern rsync, you specify -d instead of -r to copy directories by
name, or the immediate contents of a di
On Wed, Aug 02, 2006 at 02:30:29PM -0400, Erik Jacobs wrote:
> It works and lists fine. But if I choose a wildcard which contains a LOT of
> files: rsync [EMAIL PROTECTED]::filefolder/.7.*
> I get error in rsync protocol data stream (code 12)
Older rsync versions had a limit of 1000 filenames
Erik,
Include/exclude rules that you specify earlier have higher priority.
If you say --exclude="*" --include=".*", all the files will match the
first rule, and they will all get excluded. You probably want to put
the include rule first.
To transfer the immediate contents of a directory without
org
Subject: Re: code 12 error when specifying files
On Thu 03 Aug 2006, nathan r. hruby wrote:
> >
> >It's not what I'm seeing:
> >
>
> Hurm. What OS are you running this on?
Hint: check my email address :-)
> After upgrading my local/receiver rsync to 2.6.8
On Thu, 3 Aug 2006, Paul Slootman wrote:
On Thu 03 Aug 2006, nathan r. hruby wrote:
It's not what I'm seeing:
Hurm. What OS are you running this on?
Hint: check my email address :-)
Heh. Just checking :)
After upgrading my local/receiver rsync to 2.6.8 I get this:
local# rsync rem
t what files to include?
-Erik
-Original Message-
From: nathan r. hruby [mailto:[EMAIL PROTECTED]
Sent: Thursday, August 03, 2006 9:55 AM
To: rsync@lists.samba.org
Subject: Re: code 12 error when specifying files
On Thu, 3 Aug 2006, Paul Slootman wrote:
> On Thu 03 Aug 2006, nat
On Thu 03 Aug 2006, nathan r. hruby wrote:
> >
> >It's not what I'm seeing:
> >
>
> Hurm. What OS are you running this on?
Hint: check my email address :-)
> After upgrading my local/receiver rsync to 2.6.8 I get this:
>
> local# rsync remote::users/grp012/12/nhruby/public_html/
> drwxr-xr-x
On Thu, 3 Aug 2006, Paul Slootman wrote:
On Thu 03 Aug 2006, nathan r. hruby wrote:
From the manpage:
Note also that host and module references don't require a trailing
slash to copy the contents of the default directory.
So in this case the trailing slash wouldn't make a differenc
On Thu 03 Aug 2006, nathan r. hruby wrote:
> >
> >>From the manpage:
> >
> > Note also that host and module references don't require a trailing
> > slash to copy the contents of the default directory.
> >
> >So in this case the trailing slash wouldn't make a difference.
>
> In my case I'm
On Thu, 3 Aug 2006, nathan r. hruby wrote:
For example, for module x with path set to /home, tying to sync the
contents of "server::home/user1/public_html/" yields me the directory
public_html, the the files within it.
s/::home/::x/
Someday I'll learn to type like a big person :)
-n
--
-
On Thu, 3 Aug 2006, Paul Slootman wrote:
On Thu 03 Aug 2006, nathan r. hruby wrote:
I have to agree, I see the same behavior when using rsyncd transport
instead of ssh transport (as Erik is): trailing slashes seem to be
ignored, and instead of directory contents, you get the directory name.
BTW, I see no difference when using an rsync daemon or an ssh
connection, with the given problem:
remote# mkdir /tmp/test; cd /tmp/test; touch a b c .a .b .c
remote# ls -la
total 0
drwxr-xr-x 2 root root 57 Aug 3 15:06 .
drwxrwxrwt 3 root root 80 Aug 3 15:05 ..
-rw-r--r-- 1 root root 0 Aug
ry if someone would be
willing to help me sort out the error messages I will undoubtedly receive :)
-Erik
-Original Message-
From: Paul Slootman [mailto:[EMAIL PROTECTED]
Sent: Thursday, August 03, 2006 8:58 AM
To: rsync@lists.samba.org
Subject: Re: code 12 error when specifying files
On Thu 03 Aug 2006, nathan r. hruby wrote:
>
> I have to agree, I see the same behavior when using rsyncd transport
> instead of ssh transport (as Erik is): trailing slashes seem to be
> ignored, and instead of directory contents, you get the directory name.
>From the manpage:
Note also that
On Thu, 3 Aug 2006, Erik Jacobs wrote:
Paul,
Almost all permutations of trailing slashes and no trailing slashes seem to
produce the same results...
I have to agree, I see the same behavior when using rsyncd transport
instead of ssh transport (as Erik is): trailing slashes seem to be
ignored
IL PROTECTED]
Sent: Thursday, August 03, 2006 8:29 AM
To: rsync@lists.samba.org; Matt McCutchen
Subject: Re: code 12 error when specifying files
On Thu 03 Aug 2006, Erik Jacobs wrote:
>
> That works brilliantly, but I think I'm still doing something wrong.
>
> rsync --exclude=&qu
On Thu 03 Aug 2006, Erik Jacobs wrote:
>
> That works brilliantly, but I think I'm still doing something wrong.
>
> rsync --exclude="*" --include=".*" -Lputzogv [EMAIL PROTECTED]::folder
> /home/user/folder
>
> result:
> client: nothing to do: perhaps you need to specify some filenames or the
to solve this problem... but I can't do that anymore because that's what's
causing the problem in the first place...
Ideas?
-Erik
-Original Message-
From: Matt McCutchen [mailto:[EMAIL PROTECTED]
Sent: Wednesday, August 02, 2006 5:54 PM
To: Erik Jacobs
Cc: rsync
Subject: Re
On 8/2/06, Erik Jacobs <[EMAIL PROTECTED]> wrote:
We have a file structure on our servers which involves a folder that contains
hundreds of info files about particular things that all look like this format:
.a.b.c(.old/.new)
But if I choose a wildcard which contains a LOT of files:
rsync [
21 matches
Mail list logo
