Re: exclude this file #notes#
Harry Putnam [EMAIL PROTECTED] wrote: What is the necessary syntax to exclude a file named #notes# from an action? I've tried these without success: #* #* #notes# #notes# \#notes\# there's an old message where Dave said: On Thu, Nov 15, 2001 at 05:17:32PM +0100, Thomas Schweikle wrote: ... Wait, if i386* matches directories and not just files you'll need + /iso + /iso/1.5.* + /iso/1.5.*/i386** - * so that it will include all files below the i386* directories. Any double asterisk in a pattern tells the matching routine to go beyond slashes. No. No solution. No files. Nothing. Definitively something wrong with these matching routines. There is one known bug with the matching routines, described at http://lists.samba.org/pipermail/rsync/1999-October/001440.html but you're not hitting it because it's only when patterns don't begin with a slash. Other than that, the only thing wrong with them is that they are hard to understand and aren't as flexible as many people would like, but again, they're flexible enough for your situation. Did you try my less simple example with the 6 patterns? Did you try applying the patch that gives more debugging information? Here's another idea: try running it without the - * and with a -n (to not actually copy) and see some of the file names -v prints out; could they match some of your patterns except for the beginning /? I was assuming your patterns began with iso because of the examples you gave, but I see in looking back that the command line you gave had a iso/ in the source which means that iso would not be included in the path, so you would just use + /1.5.* + /1.5.*/i386** - * I just ran that list against ftp3.sourceforge.net::netbsd/iso/ and it worked. - Dave Dykstra end Since your patterns do not begin with a slash, I'd go look at the url above and see if it helps you any. Post back here if the above random stuff I dug up does not help, and someone with a clue will do a better job than I ;-) rc
Re: exclude this file #notes#
On Wed, Jan 09, 2002 at 10:34:23PM -0800, Harry Putnam wrote: What is the necessary syntax to exclude a file named #notes# from an action? I've tried these without success: #* #* #notes# #notes# \#notes\# The man page says lines beginning with # in an --exclude-from file are ignored. You could use --exclude #from# on the command line, or you could do something that would remove the '#' from the first character in an exclude-from file. Quotes and backslashes are not recognized in the file. You could try '*#notes#', or if the file is at your top level directory you could use '/#notes#'. - Dave Dykstra
Re: exclude this file #notes#
On Thu, Jan 10, 2002 at 08:57:03AM -0600, Dave Dykstra wrote: On Wed, Jan 09, 2002 at 10:34:23PM -0800, Harry Putnam wrote: What is the necessary syntax to exclude a file named #notes# from an action? I've tried these without success: #* #* #notes# #notes# \#notes\# The man page says lines beginning with # in an --exclude-from file are ignored. You could use --exclude #from# on the command line, or you could do something that would remove the '#' from the first character in an exclude-from file. Quotes and backslashes are not recognized in the file. You could try '*#notes#', or if the file is at your top level directory you could use '/#notes#'. Oh yeah, Rusty's posting reminded me of another possibility; these two together should be completely equivalent to the command line --exclude '#notes#': /#notes# /**/#notes# - Dave
Re: rsync tree migration in progress
This looks like too much pain to justify the switch at the moment. I'm going to at least hold it over for a while. Sorry for any inconvenience. -- Martin
rsync 2.5.1 server - strange logs
I've just upgraded my rsync server to 2.5.1 (before, I was using 2.4.6), without changing anything in /etc/rsyncd.conf, and now, I have this logs each time a client connect to server: 2002/01/07 18:33:03 [10432] rsync: reverse name lookup mismatch on fd3 - spoofed address? 2002/01/07 18:33:03 [10432] rsync on admin/sbin/padmin_update.sh from UNKNOWN (172.16.65.14) 2002/01/07 18:33:03 [10432] wrote 79 bytes read 88 bytes total size 1494 The server configuration has not changed since upgrading to rsync 2.5.1. No noticed network configuration problem. Here is /etc/rsyncd.conf: log file = /var/log/rsyncd.log pid file = /var/run/rsyncd.pid [admin] uid = root gid = root path = /DT/PROD/admin comment = production administrator files read only = true [admin-dev] uid = root gid = root path = /DT/PROD/admin-dev comment = production administrator files (dev) read only = true [bbserver] uid = root gid = root path = /DT/PROD/bbserver comment = Big Brother server read only = true hosts allow = anakin.orsay.quadratec.fr palpatine.orsay.quadratec.fr [apps] uid = root gid = root path = /opt comment = applications read only = true hosts allow = palpatine.orsay.quadratec.fr Should I change something in rsyncd.conf ? Laurent. -- Laurent CREPET -- [EMAIL PROTECTED] http://www.megrapet.org/