rsync - Jan 2005 - Rsync Minimalist: --include only does "add_exclude"

Why does this not include?  I have tried many variations including 
adding an exclude command.

Includes.txt:
+ //aBackup/*
+ //apic/*
- /*

rsync --verbose --progress --stats -vv --recursive -e "ssh -p 2423" 
--include-from=includes.txt rsynchost:
add_exclude(+ //aBackup/*.*)
add_exclude(+ //apic/*)
add_exclude(- /*)
user@rsynchost's password:
receiving file list ... add_exclude(+ //aBackup/*.*,exclude)
add_exclude(+ //apic/*,exclude)
add_exclude(/*,exclude)
server_sender starting pid=9646
make_file(1,.)
expand file_list to 4000 bytes, did move
recv_file_name(.)
excluding directory .kde because of pattern /*
excluding file .emacs because of pattern /*
excluding file .bash_logout because of pattern /*
excluding file .bash_profile because of pattern /*
excluding file .bashrc because of pattern /*
excluding file .gtkrc because of pattern /*
excluding file .bash_history because of pattern /*
excluding file .viminfo because of pattern /*
received 1 names
done
drwxr-xr-x        4096 2005/01/16  .
recv_file_list done
get_local_name count=1 <NULL>
generator starting pid=2988 count=1
generate_files phase=1
recv_files(1) starting
send_file_list done
send_files starting
recv_files phase=1
generate_files phase=2
send_files phase=1
send files finished
total: matches=0  tag_hits=0  false_alarms=0 data=0
recv_files finished

Number of files: 1
Number of files transferred: 0
Total file size: 0 bytes
Total transferred file size: 0 bytes
Literal data: 0 bytes
Matched data: 0 bytes
File list size: 20
Total bytes written: 55
Total bytes read: 802

wrote 55 bytes  read 802 bytes  155.82 bytes/sec
total size is 0  speedup is 0.00

C:\abackup>Pause
Press any key to continue . . .

Regards
MikeT

On Tue, 18 Jan 2005, Mike Todd <Mike@toddco.net>
wrote:
>
> Why does this not include?  I have tried many variations including
> adding an exclude command.
> 
> Includes.txt:
> + //aBackup/*
> + //apic/*
> - /*
As Wayne pointed out, you are not matching anything by those names
in the rsync source directory, which is *not necesarily* the root
directory.  You don't need double slashes, btw.
> rsync --verbose --progress --stats -vv --recursive -e "ssh -p
2423"
> --include-from=includes.txt rsynchost:
Thanks for including the actual command this time.  It helps a lot.

Your source directory is your home directory on "rsynchost:".
This is *not* the root directory on the source system, which is
apparently where the aBackup directory is located.

Include/exclude paths with leading slashes are still relative to the
source/target directories - they are not absolute filesystem paths.
So /aBackup/ refers to an aBackup subdirectory in your home directory.

Also - you don't specify a target - so rsync will just give you a
listing of file information (like ls -l).

[ snip ]
> excluding directory .kde because of pattern /*
> excluding file .emacs because of pattern /*
> excluding file .bash_logout because of pattern /*
> excluding file .bash_profile because of pattern /*
> excluding file .bashrc because of pattern /*
> excluding file .gtkrc because of pattern /*
> excluding file .bash_history because of pattern /*
> excluding file .viminfo because of pattern /*
Those are all from your home directory, no?  Nothing matches
your include-from patterns, so you only get the home directory.
> received 1 names
> done
> drwxr-xr-x        4096 2005/01/16  .
That is the "ls -l" output from rsync for the source directory.
That is the only output since everything else was excluded.

[ snip ]
> C:\abackup>Pause
> Press any key to continue . . .
That is why I think that your aBackup directory is in the root
directory on rsyncsource:.

If you want to copy /aBackup/, etc. from rsyncsource: to /aBackup/,
etc. on your local machine, specify the root directory on the
source and the target:

  rsync --verbose --progress --stats -vv --recursive -e "ssh -p 2423"
  --include-from=includes.txt rsynchost:/ /
                                        ^ ^
But using a root directory for a target can be very dangerous if
you later add --delete and don't get things quite right.

I strongly suggest always using --dry-run (or -n) to test things out.
-- 
        John Van Essen  Univ of MN Alumnus  <vanes002@umn.edu>