Re: filelist calculation algoritm
jw schultz wrote: On Tue, Jan 07, 2003 at 07:15:27PM +0100, Lorenzo Bettini wrote: Aaron Morris wrote: You did not specifically mention it: compression (-z) would probably help more than anything. Otherwise, you could do something like: Have a file (ie filelist.txt) that contains the filename (with relative paths), one file per line. rsync -rRWz `cat filelist.txt` user@hostname::module as I understand this works only when connecting to a rsync daemon... what if I wanted to use ssh as a shell? Compression works fine over ssh. Don't know where you got the impression it doesn't given what is in the manpage. I did not refer to compression: I was wondering if there's a way for updating only a list of files with the `cat` trick... Lorenzo -- +-+ | Lorenzo Bettini ICQ# lbetto, 16080134 | | PhD student in Computer Science| | Dip. Sistemi e Informatica, Univ. di Firenze | | Tel +39 055 4796741, Fax +39 055 4796730 | | Florence - Italy (Linux User # 158233) | | Home Page: http://www.lorenzobettini.it| | E-Mail : [EMAIL PROTECTED]| | http://music.dsi.unifi.it XKlaim language | | http://www.lorenzobettini.it/purpleCover Band | | http://www.gnu.org/software/src-highlite | | http://www.gnu.org/software/gengetopt | +-+ -- To unsubscribe or change options: http://lists.samba.org/mailman/listinfo/rsync Before posting, read: http://www.tuxedo.org/~esr/faqs/smart-questions.html
Re: filelist calculation algoritm
On Wed, Jan 08, 2003 at 09:42:39AM +0100, Lorenzo Bettini wrote: > jw schultz wrote: > >On Tue, Jan 07, 2003 at 07:15:27PM +0100, Lorenzo Bettini wrote: > > > >>Aaron Morris wrote: > >> > >>>You did not specifically mention it: compression (-z) would probably > >>>help more than anything. Otherwise, you could do something like: > >>> > >>>Have a file (ie filelist.txt) that contains the filename (with relative > >>>paths), one file per line. > >>> > >>>rsync -rRWz `cat filelist.txt` user@hostname::module > >>> > >> > >>as I understand this works only when connecting to a rsync daemon... > >>what if I wanted to use ssh as a shell? > > > > > >Compression works fine over ssh. Don't know where you got > >the impression it doesn't given what is in the manpage. > > > > I did not refer to compression: I was wondering if there's a way for > updating only a list of files with the `cat` trick... Sorry. I just couldn't imagine the command substitution not working. It is a property of the shell, not rsync. Actually, in the case of a pull operation it won't work with a daemon but will via remote shell (ssh, rsh, etc) as the remote rsync command line will be executed via a shell which will be able to do command substitution. It is just a matter of quoting to defer interpolation. This was addressed a couple of months ago on this list. The one drawback to this method of dealing with a list is that it will flatten it. Each item in the list will be synced to the same destination as though you had run separate rsync commands. -- J.W. SchultzPegasystems Technologies email address: [EMAIL PROTECTED] Remember Cernan and Schmitt -- To unsubscribe or change options: http://lists.samba.org/mailman/listinfo/rsync Before posting, read: http://www.tuxedo.org/~esr/faqs/smart-questions.html
rsync over ssh: failed to connect to... after SuSE update
I have been running rsync over ssh to a remote server without problems for months. After an update from SuSE 7.2 to 8.1, I always get the following error: "rsync: failed to connect to localhost: Connection refused rsync error: error in socket IO (code 10) at clientserver.c(97)" Details: the rsync server port 873 is forwarded to 8073 on the client, so the client connects to the server as localhost:8073. The ssh-connection seems to work, because I can do a remote-login and issue commands on the remote server. With a running ssh-connection, I tried to connect to the forwarded port with telnet and got the following results: telnet: connect to address 127.0.0.1: Connection refused (in local telnet window: when trying forwarded port 8073 -> 873) channel_open_failure: 2: reason 2 Connection refused (in remote ssh window: when trying forwarded port 5908 -> 5908) ssh-command for the connection: su - -c \ "/usr/bin/ssh -l USER1 -C -p 69 SERVER1 \ -L 5908:IP1:5908 \ -L 8073:IP2:873" where USER1 is the username for the connection (local and remote are identical) SERVER1 is the server address IP1 and IP2 are IP-Adresses of forwarded servers. rsync-command for the connection: rsync -v --port=8073 --password-file=/etc/PASSWDFILE localhost::(...) where PASSWDFILE is the crypted password for the rsync-connection (...) are the share-names of the rsync-server. Probably there is a problem on my local system after the system update, because all this worked fine before. Trying the older ssh and rsync-versions leads to the same results. Anybody an idea about that? Thanks in advance Klaus. -- To unsubscribe or change options: http://lists.samba.org/mailman/listinfo/rsync Before posting, read: http://www.tuxedo.org/~esr/faqs/smart-questions.html
Re: IPv6 hosts allow|deny
On Wed, Jan 08, 2003 at 12:25:15AM +0100, Bert Vermeulen wrote: > On Tue, 7 Jan 2003, Dave Dykstra wrote: > > > Even though rsync maintenance isn't as bad as wget's, the maintainers > > are all VERY part time so that is a big part of the problem. Most of us > > don't have ipv6 systems to test things on. Can you vouch for the quality > > of the patch? I was able to get it with > > > > wget --passive >ftp://ftp.linux-ipv6.org/pub/usagi/misc/rsync-2_5_5-v6auth-20021016.patch.gz > > > > and it looks quite extensive. > > Yes, it's very extensive, and there's some code in there that's pretty > advanced. > > The fact of the matter is, I made my own patch for this functionality first, > and only then noticed Hideaki's patch -- and his, while not as readable to > the casual observer, seems like better code. He is rewriting the linux > kernel IPv6 stack, so I'd expect his rsync patch to be decent :-) > > Nevertheless, feel free to take a look at my patch: > http://biot.com/patches/rsync-ipv6-acl.patch > > So I haven't used Hideaki's patch, but I use mine, and it's good. Please do > apply one of them however. Since you're more familiar with that area of the code than any of the rsync maintainers and you think his patch is better, please test out his patch and look it over to see if you think there should be any changes. In particular, I see that yours includes documentation changes and his doesn't. - Dave -- To unsubscribe or change options: http://lists.samba.org/mailman/listinfo/rsync Before posting, read: http://www.tuxedo.org/~esr/faqs/smart-questions.html
Re: Not preserving permissions really preserves some
On Wed, Jan 08, 2003 at 03:08:38PM +1100, [EMAIL PROTECTED] wrote: > > > Thanks for the reply. > > I did see this on the to-do list, and thought that it might > be a preferable solution (just a bit more work). > It would be messy to do the xargs stuff as I am running rsync > over ssh with restricted commands based upon keys :-) > > Questions: >1. Is the proposed solution in the todo (--chmod) agreed? Yes. >2. Is anyone actively working on it? No. >3. If I wrote the patch to support the --chmod as outlined > in the todo file, would someone apply it (assuming my > code was okay ;-) ? Yes, although probably not in the very next release, probably in 2.6.0, unless the changes ended up being very isolated and we could clearly see there was very little risk in breaking something else. >4. Should the patch be applied to the "head", or should it > be against the latest release version? To the CVS "head". - Dave -- To unsubscribe or change options: http://lists.samba.org/mailman/listinfo/rsync Before posting, read: http://www.tuxedo.org/~esr/faqs/smart-questions.html
Re: directories that change into symlinks
Dave Dykstra wrote: Could you please post your full command line and say where in the directory structure the directories were replaced by symlinks? I have not yet been able to come up with an example where --force makes a difference when using --delete and -r (or -a). Refer to http://lists.samba.org/pipermail/rsync/2002-January/005971.html this is the 'old' directory (the one that will become a mirror of the 'new' dir). note that dir3 is still a directory and dir3 is not empty: === [dave@builder old]$ ls -laR ..: total 0 drwxrwxr-x4 dave dave120 Jan 5 07:12 . drwxrwxr-x5 dave dave120 Jan 5 07:13 .. lrwxrwxrwx1 dave dave 4 Jan 5 07:12 dir1 -> dir2 drwxrwxr-x4 dave dave 96 Jan 5 07:11 dir2 drwxrwxr-x2 dave dave 72 Jan 5 07:12 dir3 ../dir2: total 0 drwxrwxr-x4 dave dave 96 Jan 5 07:11 . drwxrwxr-x4 dave dave120 Jan 5 07:12 .. drwxrwxr-x2 dave dave 72 Jan 5 07:11 dir11 drwxrwxr-x2 dave dave 72 Jan 5 07:11 dir12 ../dir2/dir11: total 0 drwxrwxr-x2 dave dave 72 Jan 5 07:11 . drwxrwxr-x4 dave dave 96 Jan 5 07:11 .. -rw-rw-r--1 dave dave 0 Jan 5 07:11 file1 ../dir2/dir12: total 0 drwxrwxr-x2 dave dave 72 Jan 5 07:11 . drwxrwxr-x4 dave dave 96 Jan 5 07:11 .. -rw-rw-r--1 dave dave 0 Jan 5 07:11 file2 ../dir3: total 0 drwxrwxr-x2 dave dave 72 Jan 5 07:12 . drwxrwxr-x4 dave dave120 Jan 5 07:12 .. -rw-rw-r--1 dave dave 0 Jan 5 07:12 file3 === this is the 'new' directory (the one that will be mirrored by the 'old'). note that 'dir3' is now a symlink instead of a dir. === [dave@builder new]$ ls -laR ..: total 0 drwxrwxr-x4 dave dave120 Jan 5 07:13 . drwxrwxr-x5 dave dave120 Jan 5 07:13 .. drwxrwxr-x4 dave dave 96 Jan 5 07:11 dir1 drwxrwxr-x2 dave dave 48 Jan 5 07:11 dir2 lrwxrwxrwx1 dave dave 4 Jan 5 07:11 dir3 -> dir1 ../dir1: total 0 drwxrwxr-x4 dave dave 96 Jan 5 07:11 . drwxrwxr-x4 dave dave120 Jan 5 07:13 .. drwxrwxr-x2 dave dave 72 Jan 5 07:11 dir11 drwxrwxr-x2 dave dave 72 Jan 5 07:11 dir12 ../dir1/dir11: total 0 drwxrwxr-x2 dave dave 72 Jan 5 07:11 . drwxrwxr-x4 dave dave 96 Jan 5 07:11 .. -rw-rw-r--1 dave dave 0 Jan 5 07:11 file1 ../dir1/dir12: total 0 drwxrwxr-x2 dave dave 72 Jan 5 07:11 . drwxrwxr-x4 dave dave 96 Jan 5 07:11 .. -rw-rw-r--1 dave dave 0 Jan 5 07:11 file2 ../dir2: total 0 drwxrwxr-x2 dave dave 48 Jan 5 07:11 . drwxrwxr-x4 dave dave120 Jan 5 07:13 .. === now compare these two commands. i find that the second one works. $ rsync -avz new/* old/ $ rsync -avz --force new/* old/ -- dave -- To unsubscribe or change options: http://lists.samba.org/mailman/listinfo/rsync Before posting, read: http://www.tuxedo.org/~esr/faqs/smart-questions.html
Re: directories that change into symlinks
Yes, I knew --force made a difference when not using --delete (that's very much like the example in the message I referred to), and I think it's good that way and --force should not be the default without --delete. I thought you were using --delete. If --force makes a difference in any case that --delete is used (and so far I have been unable to find any such case), I think it would make sense for --force to be automatically turned on by --delete. - Dave On Wed, Jan 08, 2003 at 07:39:22AM -0700, David Garamond wrote: > Dave Dykstra wrote: > >Could you please post your full command line and say where in the directory > >structure the directories were replaced by symlinks? I have not yet been > >able to come up with an example where --force makes a difference when > >using --delete and -r (or -a). Refer to > >http://lists.samba.org/pipermail/rsync/2002-January/005971.html > > this is the 'old' directory (the one that will become a mirror of the > 'new' dir). note that dir3 is still a directory and dir3 is not empty: > === > [dave@builder old]$ ls -laR > ...: > total 0 > drwxrwxr-x4 dave dave120 Jan 5 07:12 . > drwxrwxr-x5 dave dave120 Jan 5 07:13 .. > lrwxrwxrwx1 dave dave 4 Jan 5 07:12 dir1 -> dir2 > drwxrwxr-x4 dave dave 96 Jan 5 07:11 dir2 > drwxrwxr-x2 dave dave 72 Jan 5 07:12 dir3 > > .../dir2: > total 0 > drwxrwxr-x4 dave dave 96 Jan 5 07:11 . > drwxrwxr-x4 dave dave120 Jan 5 07:12 .. > drwxrwxr-x2 dave dave 72 Jan 5 07:11 dir11 > drwxrwxr-x2 dave dave 72 Jan 5 07:11 dir12 > > .../dir2/dir11: > total 0 > drwxrwxr-x2 dave dave 72 Jan 5 07:11 . > drwxrwxr-x4 dave dave 96 Jan 5 07:11 .. > -rw-rw-r--1 dave dave 0 Jan 5 07:11 file1 > > .../dir2/dir12: > total 0 > drwxrwxr-x2 dave dave 72 Jan 5 07:11 . > drwxrwxr-x4 dave dave 96 Jan 5 07:11 .. > -rw-rw-r--1 dave dave 0 Jan 5 07:11 file2 > > .../dir3: > total 0 > drwxrwxr-x2 dave dave 72 Jan 5 07:12 . > drwxrwxr-x4 dave dave120 Jan 5 07:12 .. > -rw-rw-r--1 dave dave 0 Jan 5 07:12 file3 > === > > this is the 'new' directory (the one that will be mirrored by the > 'old'). note that 'dir3' is now a symlink instead of a dir. > > === > [dave@builder new]$ ls -laR > ...: > total 0 > drwxrwxr-x4 dave dave120 Jan 5 07:13 . > drwxrwxr-x5 dave dave120 Jan 5 07:13 .. > drwxrwxr-x4 dave dave 96 Jan 5 07:11 dir1 > drwxrwxr-x2 dave dave 48 Jan 5 07:11 dir2 > lrwxrwxrwx1 dave dave 4 Jan 5 07:11 dir3 -> dir1 > > .../dir1: > total 0 > drwxrwxr-x4 dave dave 96 Jan 5 07:11 . > drwxrwxr-x4 dave dave120 Jan 5 07:13 .. > drwxrwxr-x2 dave dave 72 Jan 5 07:11 dir11 > drwxrwxr-x2 dave dave 72 Jan 5 07:11 dir12 > > .../dir1/dir11: > total 0 > drwxrwxr-x2 dave dave 72 Jan 5 07:11 . > drwxrwxr-x4 dave dave 96 Jan 5 07:11 .. > -rw-rw-r--1 dave dave 0 Jan 5 07:11 file1 > > .../dir1/dir12: > total 0 > drwxrwxr-x2 dave dave 72 Jan 5 07:11 . > drwxrwxr-x4 dave dave 96 Jan 5 07:11 .. > -rw-rw-r--1 dave dave 0 Jan 5 07:11 file2 > > .../dir2: > total 0 > drwxrwxr-x2 dave dave 48 Jan 5 07:11 . > drwxrwxr-x4 dave dave120 Jan 5 07:13 .. > === > > now compare these two commands. i find that the second one works. > > $ rsync -avz new/* old/ > $ rsync -avz --force new/* old/ > > -- > dave -- To unsubscribe or change options: http://lists.samba.org/mailman/listinfo/rsync Before posting, read: http://www.tuxedo.org/~esr/faqs/smart-questions.html
long directory name problem
Does rsync has directory name length limit? I was trying to rsync a directory that has the name length of 34 characters and getting permission denied error. $ rsync -avz --delete --force -e ssh /usr/local/apache/htdocs 192.168.0.2:/usr/local/apache building file list ... readlink htdocs/CorporateLegalTimesEDITORIAL_files/cBug_blueXs.gif: Permission denied readlink httpd/html/CorporateLegalTimesEDITORIAL_files/title_a.gif: Permission denied When I rename the directory to about half of its original length, the error goes away. Any advise are appreciated. -- ER
Rsync and windows
Hi there, I have a problem syncronizing a windows machine with a linux box. I want to backup the "My Documents" folder. Therefore I burned the data on a cdrom because the windows pc is only connected over a slow wan connection to the linux box. When I copy the data to the users home directory (using samba and another windows pc) and run the rsync program all the files are copied once more. I made some tests and changed the ownership and the also the file permissions for the copied data on the linux box but still rsync wants to transfer all the data, even if they look exactly the same after the transfer. If I use rsync to copy the data for the first time everything works fine. On the windows machine (Win2000 SP3) I run rsync 2.5.1 protocol version 25 in a cygwin environement. The linux box runs RedHat 7.3 with rsync version 2.5.5 protocol version 26. The connections runs for security reasons over a ssh tunnel. Is there a simple way to burn windows data on a cdrom, then to the right directory on the linux machine and run rsync without transfering the whole data once again ? Please help and thanks in advance. O. Krehan -- To unsubscribe or change options: http://lists.samba.org/mailman/listinfo/rsync Before posting, read: http://www.tuxedo.org/~esr/faqs/smart-questions.html
Re: Rsync and windows
On Wed, Jan 08, 2003 at 05:16:21PM +0100, Oliver Krehan wrote: > Hi there, > > I have a problem syncronizing a windows machine with a linux box. > I want to backup the "My Documents" folder. Therefore I burned the data > on a cdrom because the windows pc is only connected over a slow wan > connection to the linux box. When I copy the data to the users home > directory (using samba and another windows pc) and run the rsync program > all the files are copied once more. I made some tests and changed the > ownership and the also the file permissions for the copied data on the > linux box but still rsync wants to transfer all the data, even if they > look exactly the same after the transfer. If I use rsync to copy the > data for the first time everything works fine. > > On the windows machine (Win2000 SP3) I run rsync 2.5.1 protocol version > 25 in a cygwin environement. The linux box runs RedHat 7.3 with rsync > version 2.5.5 protocol version 26. The connections runs for security > reasons over a ssh tunnel. > > Is there a simple way to burn windows data on a cdrom, then to the right > directory on the linux machine and run rsync without transfering the > whole data once again ? You've not shown your rsync commands nor how the CD was burned, nor how you mounted and copied the CD. Using the CD you probably lost all metadata. In particular, you lost the modification times. Although rsync is reporting transferring all the files, unless you are messing up the trees it should be just syncing all the files. That means it isn't actually transferring the data, just doing the rsync's magic to confirm the file is unchanged. You would have better luck if you used tar or another archive tool to create a file (preserving mod-times) to burn and then extract that archive to the destination. -- J.W. SchultzPegasystems Technologies email address: [EMAIL PROTECTED] Remember Cernan and Schmitt -- To unsubscribe or change options: http://lists.samba.org/mailman/listinfo/rsync Before posting, read: http://www.tuxedo.org/~esr/faqs/smart-questions.html
Re: long directory name problem
I've never heard of a name length limit. One operating system(s) and rsync version(s) are you using? - Dave On Wed, Jan 08, 2003 at 07:32:19AM -0800, elijah reyen wrote: > Does rsync has directory name length limit? I was trying to rsync a directory that >has the name length of 34 characters and getting permission denied error. > > $ rsync -avz --delete --force -e ssh /usr/local/apache/htdocs >192.168.0.2:/usr/local/apache > building file list ... > readlink htdocs/CorporateLegalTimesEDITORIAL_files/cBug_blueXs.gif: Permission denied > readlink httpd/html/CorporateLegalTimesEDITORIAL_files/title_a.gif: Permission denied > > When I rename the directory to about half of its original length, the error goes >away. Any advise are appreciated. > -- > ER -- To unsubscribe or change options: http://lists.samba.org/mailman/listinfo/rsync Before posting, read: http://www.tuxedo.org/~esr/faqs/smart-questions.html
Re: long directory name problem
We experience that as well. We use (sadly) Rsycn in Win32 environment. I hear it's due to the Cygwin utilities. Rgds, Bart Coninckx Network Administrator CNE, ASE * Sita ICT Services Lilsedijk 19 B-2340 Beerse Belgium e-mail: [EMAIL PROTECTED] Tel: + 32 (0) 14 62 28 22 Fax: + 32 (0) 14 62 41 47 * Dave Dykstra <[EMAIL PROTECTED]To: elijah reyen <[EMAIL PROTECTED]> >cc: [EMAIL PROTECTED] Sent by: Subject: Re: long directory name problem rsync-admin@lists .samba.org 01/08/2003 21:17 I've never heard of a name length limit. One operating system(s) and rsync version(s) are you using? - Dave On Wed, Jan 08, 2003 at 07:32:19AM -0800, elijah reyen wrote: > Does rsync has directory name length limit? I was trying to rsync a directory that has the name length of 34 characters and getting permission denied error. > > $ rsync -avz --delete --force -e ssh /usr/local/apache/htdocs 192.168.0.2:/usr/local/apache > building file list ... > readlink htdocs/CorporateLegalTimesEDITORIAL_files/cBug_blueXs.gif: Permission denied > readlink httpd/html/CorporateLegalTimesEDITORIAL_files/title_a.gif: Permission denied > > When I rename the directory to about half of its original length, the error goes away. Any advise are appreciated. > -- > ER -- To unsubscribe or change options: http://lists.samba.org/mailman/listinfo/rsync Before posting, read: http://www.tuxedo.org/~esr/faqs/smart-questions.html -- To unsubscribe or change options: http://lists.samba.org/mailman/listinfo/rsync Before posting, read: http://www.tuxedo.org/~esr/faqs/smart-questions.html
Re: long directory name problem
On Wed, Jan 08, 2003 at 02:17:16PM -0600, Dave Dykstra wrote: > I've never heard of a name length limit. One operating system(s) and rsync > version(s) are you using? > > - Dave > > On Wed, Jan 08, 2003 at 07:32:19AM -0800, elijah reyen wrote: > > Does rsync has directory name length limit? I was > > trying to rsync a directory that has the name length of > > 34 characters and getting permission denied error. > > > > $ rsync -avz --delete --force -e ssh > > /usr/local/apache/htdocs 192.168.0.2:/usr/local/apache > > building file list ... readlink > > htdocs/CorporateLegalTimesEDITORIAL_files/cBug_blueXs.gif: > > Permission denied readlink > > httpd/html/CorporateLegalTimesEDITORIAL_files/title_a.gif: > > Permission denied > > > > When I rename the directory to about half of its > > original length, the error goes away. Any advise are > > appreciated. You aren't hitting an rsync limit. The only limit existing in rsync is MAXPATHLEN which if not defined by the libs will be 1024. Whatever is doing it seems to have a bug in any case. readlink or stat should return set errno to ENOENT, ENAMETOOLONG, or ENOTDIR depending on what is actually causing the error. EACCESS means the file is there and the path is good, you just don't have permission. Most likely it is the libraries causing the problem. In addition to the OS and rsync version question, what are the filesystem types? -- J.W. SchultzPegasystems Technologies email address: [EMAIL PROTECTED] Remember Cernan and Schmitt -- To unsubscribe or change options: http://lists.samba.org/mailman/listinfo/rsync Before posting, read: http://www.tuxedo.org/~esr/faqs/smart-questions.html
Re: filelist calculation algoritm
I do not think there would be a problem using ssh as the shell. The cat trick or using - is basically the same thing as specifying the file names manually. On Wed, 2003-01-08 at 03:42, Lorenzo Bettini wrote: > jw schultz wrote: > > On Tue, Jan 07, 2003 at 07:15:27PM +0100, Lorenzo Bettini wrote: > > > >>Aaron Morris wrote: > >> > >>>You did not specifically mention it: compression (-z) would probably > >>>help more than anything. Otherwise, you could do something like: > >>> > >>>Have a file (ie filelist.txt) that contains the filename (with relative > >>>paths), one file per line. > >>> > >>>rsync -rRWz `cat filelist.txt` user@hostname::module > >>> > >> > >>as I understand this works only when connecting to a rsync daemon... > >>what if I wanted to use ssh as a shell? > > > > > > Compression works fine over ssh. Don't know where you got > > the impression it doesn't given what is in the manpage. > > > > I did not refer to compression: I was wondering if there's a way for > updating only a list of files with the `cat` trick... > > Lorenzo > > -- > +-+ > | Lorenzo Bettini ICQ# lbetto, 16080134 | > | PhD student in Computer Science| > | Dip. Sistemi e Informatica, Univ. di Firenze | > | Tel +39 055 4796741, Fax +39 055 4796730 | > | Florence - Italy (Linux User # 158233) | > | Home Page: http://www.lorenzobettini.it| > | E-Mail : [EMAIL PROTECTED]| > | http://music.dsi.unifi.it XKlaim language | > | http://www.lorenzobettini.it/purpleCover Band | > | http://www.gnu.org/software/src-highlite | > | http://www.gnu.org/software/gengetopt | > +-+ > > > > -- > To unsubscribe or change options: http://lists.samba.org/mailman/listinfo/rsync > Before posting, read: http://www.tuxedo.org/~esr/faqs/smart-questions.html -- Aaron W Morris decep PGP Key: 259978D1 -- To unsubscribe or change options: http://lists.samba.org/mailman/listinfo/rsync Before posting, read: http://www.tuxedo.org/~esr/faqs/smart-questions.html
Proper --exclude= syntax?
I'm currently syncing the home directories on two boxes with the syntax: dest-host# rsync -av -e "ssh" --delete --progress source-host:/home/ /home/ That's working well. Now I want to exclude /home/httpd/* from the process. (I don't want web changes on one box to affect the other box.) Which of the following is the best/correct one to use? 1) --exclude=/home/httpd/* 2) --exclude=/home/httpd/ 3) --exclude=/home/httpd 4) --exclude=httpd/* 5) --exclude=httpd/ 6) --exclude=httpd Thanks! -Dan __ Do you Yahoo!? Yahoo! Mail Plus - Powerful. Affordable. Sign up now. http://mailplus.yahoo.com -- To unsubscribe or change options: http://lists.samba.org/mailman/listinfo/rsync Before posting, read: http://www.tuxedo.org/~esr/faqs/smart-questions.html
Re: Proper --exclude= syntax?
On Wed, Jan 08, 2003 at 02:15:13PM -0800, Dan Kressin wrote: > I'm currently syncing the home directories on two boxes with the syntax: > > dest-host# rsync -av -e "ssh" --delete --progress source-host:/home/ /home/ > > That's working well. Now I want to exclude /home/httpd/* from the process. > (I don't want web changes on one box to affect the other box.) Which of the > following is the best/correct one to use? > > 1) --exclude=/home/httpd/* > 2) --exclude=/home/httpd/ > 3) --exclude=/home/httpd > 4) --exclude=httpd/* > 5) --exclude=httpd/ > 6) --exclude=httpd > None of the above. --exclude=/httpd/ Patterns are relative to the src/dest paths. The leading slash is the equivelant of a regex ^ leaving it off will match any directory named httpd however deep in the tree. -- J.W. SchultzPegasystems Technologies email address: [EMAIL PROTECTED] Remember Cernan and Schmitt -- To unsubscribe or change options: http://lists.samba.org/mailman/listinfo/rsync Before posting, read: http://www.tuxedo.org/~esr/faqs/smart-questions.html
Re: long directory name problem
[EMAIL PROTECTED] wrote: We experience that as well. We use (sadly) Rsycn in Win32 environment. I hear it's due to the Cygwin utilities. What file sysetm, cygwni version and rsync version are you talking about? $ echo "try" >ridicolouslyLongFileNameThatNoOnWillEverUseAsItIsReallyInsaneToDoButYetItWorkButImUsingNTFSHereMaybeThisIsTheIssueButWouldAnywayBeAWindowsIssueReally $ rsync -v ridicolouslyLongFileNameThatNoOnWillEverUseAsItIsReallyInsaneToDoButYetItWorkButImUsingNTFSHereMaybeThisIsTheIssueButWouldAnywayBeAWindowsIssueReally ridicolouslyLongFileNameThatNoOnWillEverUseAsItIsReallyInsaneToDoButYetItWorkButImUsingNTFSHereMaybeThisIsTheIssueButWouldAnywayBeAWindowsIssueReally2 ridicolouslyLongFileNameThatNoOnWillEverUseAsItIsReallyInsaneToDoButYetItWorkButImUsingNTFSHereMaybeThisIsTheIssueButWouldAnywayBeAWindowsIssueReally wrote 224 bytes read 36 bytes 27.37 bytes/sec total size is 4 speedup is 0.02 $ ls ridi* ridicolouslyLongFileNameThatNoOnWillEverUseAsItIsReallyInsaneToDoButYetItWorkButImUsingNTFSHereMaybeThisIsTheIssueButWouldAnywayBeAWindowsIssueReally ridicolouslyLongFileNameThatNoOnWillEverUseAsItIsReallyInsaneToDoButYetItWorkButImUsingNTFSHereMaybeThisIsTheIssueButWouldAnywayBeAWindowsIssueReally2 -- Lapo 'Raist' Luchini [EMAIL PROTECTED] (PGP & X.509 keys available) http://www.lapo.it (ICQ UIN: 529796) -- To unsubscribe or change options: http://lists.samba.org/mailman/listinfo/rsync Before posting, read: http://www.tuxedo.org/~esr/faqs/smart-questions.html
Re: Proper --exclude= syntax?
- Original Message - From: "Dan Kressin" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Wednesday, January 08, 2003 10:15 PM Subject: Proper --exclude= syntax? > I'm currently syncing the home directories on two boxes with the syntax: > > dest-host# rsync -av -e "ssh" --delete --progress source-host:/home/ /home/ > > That's working well. Now I want to exclude /home/httpd/* from the process. > (I don't want web changes on one box to affect the other box.) Which of the > following is the best/correct one to use? > > 1) --exclude=/home/httpd/* > 2) --exclude=/home/httpd/ > 3) --exclude=/home/httpd Won't work with command above. They refer to /home/home/httpd. > 4) --exclude=httpd/* Would sync perms on httpd, but not contents, also, would apply to all dirs called httpd anywhere in /home/. > 5) --exclude=httpd/ Would exclude all dirs called httpd anywhere in /home/. > 6) --exclude=httpd Would exclude all dirs or files called httpd anywhere in /home/. I would use --exclude=/httpd/ Max. -- To unsubscribe or change options: http://lists.samba.org/mailman/listinfo/rsync Before posting, read: http://www.tuxedo.org/~esr/faqs/smart-questions.html
[PATCH] Add .svn to the exclude list for --cvs-exclude
Hi, The attached patch adds the Subversion adm directory (.svn) to the list of excludes for the --cvs-exclude option and also updates the man page. (please CC me on replies as I'm not on this list) -- Jon "First things first -- but not necessarily in that order" -- The Doctor, "Doctor Who" diff -Nur -x 'debian*' -x shconfig -x '*~' rsync-2.5.5/exclude.c rsync-2.5.5-modified/exclude.c --- rsync-2.5.5/exclude.c 2002-02-18 19:10:28.0 + +++ rsync-2.5.5-modified/exclude.c 2003-01-08 22:41:10.0 + @@ -390,7 +390,7 @@ "tags","TAGS",".make.state",".nse_depinfo", "*~", "#*", ".#*", ",*", "*.old", "*.bak", "*.BAK", "*.orig", "*.rej", ".del-*", "*.a", "*.o", "*.obj", "*.so", "*.Z", "*.elc", "*.ln", - "core",NULL}; + "core", ".svn",NULL}; diff -Nur -x 'debian*' -x shconfig -x '*~' rsync-2.5.5/rsync.1 rsync-2.5.5-modified/rsync.1 --- rsync-2.5.5/rsync.1 2002-02-06 21:21:19.0 + +++ rsync-2.5.5-modified/rsync.12003-01-08 22:59:19.0 + @@ -640,7 +640,7 @@ .RS RCS SCCS CVS CVS\&.adm RCSLOG cvslog\&.* tags TAGS \&.make\&.state \&.nse_depinfo *~ #* \&.#* ,* *\&.old *\&.bak *\&.BAK *\&.orig *\&.rej \&.del-* -*\&.a *\&.o *\&.obj *\&.so *\&.Z *\&.elc *\&.ln core +*\&.a *\&.o *\&.obj *\&.so *\&.Z *\&.elc *\&.ln .svn core .RE .IP then files listed in a $HOME/\&.cvsignore are added to the list and any msg05974/pgp0.pgp Description: PGP signature
Re: [PATCH] Add .svn to the exclude list for --cvs-exclude
On Wed, Jan 08, 2003 at 11:24:03PM +, Jon Middleton wrote: > Hi, > > The attached patch adds the Subversion adm directory (.svn) to the > list of excludes for the --cvs-exclude option and also updates the man > page. > > (please CC me on replies as I'm not on this list) > Looks mostly good to me. I think it should apply ok as there hasn't been much change in cvs. I wonder if it shouldn't be ".svn/". I also don't care much for the inconstistant puctuation. Is the .svn directory the only addition appropriate for subversion? No new file prefixes or suffixes from update conflicts? Also, it is the rsync.yo file that needs updating. rsync.1 is derived via yodl. > -- > Jon > > "First things first -- but not necessarily in that order" > -- The Doctor, "Doctor Who" > diff -Nur -x 'debian*' -x shconfig -x '*~' rsync-2.5.5/exclude.c >rsync-2.5.5-modified/exclude.c > --- rsync-2.5.5/exclude.c 2002-02-18 19:10:28.0 + > +++ rsync-2.5.5-modified/exclude.c2003-01-08 22:41:10.0 + > @@ -390,7 +390,7 @@ >"tags","TAGS",".make.state",".nse_depinfo", >"*~", "#*", ".#*", ",*", "*.old", "*.bak", "*.BAK", "*.orig", >"*.rej", ".del-*", "*.a", "*.o", "*.obj", "*.so", "*.Z", "*.elc", "*.ln", > - "core",NULL}; > + "core", ".svn",NULL}; > > > > diff -Nur -x 'debian*' -x shconfig -x '*~' rsync-2.5.5/rsync.1 >rsync-2.5.5-modified/rsync.1 > --- rsync-2.5.5/rsync.1 2002-02-06 21:21:19.0 + > +++ rsync-2.5.5-modified/rsync.1 2003-01-08 22:59:19.0 + > @@ -640,7 +640,7 @@ > .RS > RCS SCCS CVS CVS\&.adm RCSLOG cvslog\&.* tags TAGS \&.make\&.state > \&.nse_depinfo *~ #* \&.#* ,* *\&.old *\&.bak *\&.BAK *\&.orig *\&.rej \&.del-* > -*\&.a *\&.o *\&.obj *\&.so *\&.Z *\&.elc *\&.ln core > +*\&.a *\&.o *\&.obj *\&.so *\&.Z *\&.elc *\&.ln .svn core > .RE > .IP > then files listed in a $HOME/\&.cvsignore are added to the list and any -- J.W. SchultzPegasystems Technologies email address: [EMAIL PROTECTED] Remember Cernan and Schmitt -- To unsubscribe or change options: http://lists.samba.org/mailman/listinfo/rsync Before posting, read: http://www.tuxedo.org/~esr/faqs/smart-questions.html
Re: [PATCH] Add .svn to the exclude list for --cvs-exclude
On Wed, Jan 08, 2003 at 04:00:23PM -0800, jw schultz wrote: > On Wed, Jan 08, 2003 at 11:24:03PM +, Jon Middleton wrote: > > > > The attached patch adds the Subversion adm directory (.svn) to the > > list of excludes for the --cvs-exclude option and also updates the man > > page. > I wonder if it shouldn't be ".svn/". > I also don't care much for the inconstistant puctuation. It could be ".svn/", but I just added it in the same format as the other entries in the list. > Is the .svn directory the only addition appropriate for > subversion? No new file prefixes or suffixes from update > conflicts? Subversion creates the following files durning a conflicted update *.mine *.rOLDREV *.rNEWREV where OLDREV and NEWREV are the version number of that file in the repository, but I think they are a bit too generic to be excluded. > Also, it is the rsync.yo file that needs updating. rsync.1 > is derived via yodl. I've attached a updated patch attached. -- Jon "First things first -- but not necessarily in that order" -- The Doctor, "Doctor Who" diff -Nur -x 'debian*' -x shconfig -x '*~' rsync-2.5.5/exclude.c rsync-2.5.5-modified/exclude.c --- rsync-2.5.5/exclude.c 2002-02-18 19:10:28.0 + +++ rsync-2.5.5-modified/exclude.c 2003-01-08 22:41:10.0 + @@ -390,7 +390,7 @@ "tags","TAGS",".make.state",".nse_depinfo", "*~", "#*", ".#*", ",*", "*.old", "*.bak", "*.BAK", "*.orig", "*.rej", ".del-*", "*.a", "*.o", "*.obj", "*.so", "*.Z", "*.elc", "*.ln", - "core",NULL}; + "core", ".svn",NULL}; diff -Nur -x 'debian*' -x shconfig -x '*~' rsync-2.5.5/rsync.yo rsync-2.5.5-modified/rsync.yo --- rsync-2.5.5/rsync.yo2002-02-06 21:20:49.0 + +++ rsync-2.5.5-modified/rsync.yo 2003-01-09 00:05:31.0 + @@ -551,7 +551,7 @@ quote(RCS SCCS CVS CVS.adm RCSLOG cvslog.* tags TAGS .make.state .nse_depinfo *~ #* .#* ,* *.old *.bak *.BAK *.orig *.rej .del-* -*.a *.o *.obj *.so *.Z *.elc *.ln core) +*.a *.o *.obj *.so *.Z *.elc *.ln core .svn) then files listed in a $HOME/.cvsignore are added to the list and any files listed in the CVSIGNORE environment variable (space delimited). msg05976/pgp0.pgp Description: PGP signature
Help With Restoring
Hi All, I have been using rsync to backup to a central server with a 7 day incremental script on 2 Redhat boxen. #!/bin/sh PATH=/usr/local/bin:/usr/bin:/bin DAY=`date +%A` export PATH DAY [ -d /root/emptydir ] || mkdir /root/emptydir rsync --rsh=/usr/bin/ssh --delete -a /root/emptydir/ CENTRAL_SERVER_IP:/backup2/BACKED_UP_SERVER_FQDN/$DAY rmdir /root/emptydir rsync --delete --stats --compress --recursive --times --perms --links --rsh=/usr/bin/ssh --exclude "tmp/" --exclude "dev/" --exclude "proc/" --exclude "backups/ " --delete-excluded --backup --backup-dir=/backup2/BACKED_UP_SERVER_FQDN/$DAY -a /* CENTRAL_SERVER_IP:/backup2/BACKED_UP_SERVER_FQDN/current && echo "Daily backup ran on `date`" >> /var/log/backup.log # End Script This has been working fine and I've even been able to restore files using scp from time to time. now I'm faced with a bare metal recovery cause of a botched upgrade from Redhat 7.1 to 8.0 that failed half way through. This machine was still accessible via console and ssh (putty). I signed in via ssh and ran... # cd / # scp -r CENTRAL_SERVER_IP:/backup1/BACKED_UP_SERVER_FQDN/current/.* . This was running for a while and then i lost my connection and cant reconnect. I won't have console access till the morning but any advice would be greatly appreciated. Thanks ..:..:..:..:..:..:..:..:..:..:..:..:.. Mark E. Hanze IT Solutions Consultant 845-629-1048 www.hanzehome.com
Re: long directory name problem
All,
Here is the complete picture of what I am doing:
OS: RedHat Linux 7.2 Kernel 2.4.19
Here is the script that I am running with:
#!/usr/bin/expect
spawn su - rsyncusr
expect {
"ter]\$ " {send "rsync -avz --delete --force -e ssh /usr/local/apache/htdocs
192.168.0.2:/usr/local/apache;exit\n"}
}
interact
jw schultz <[EMAIL PROTECTED]> wrote ..
> On Wed, Jan 08, 2003 at 02:17:16PM -0600, Dave Dykstra wrote:
> > I've never heard of a name length limit. One operating system(s) and
> rsync
> > version(s) are you using?
> >
> > - Dave
> >
> > On Wed, Jan 08, 2003 at 07:32:19AM -0800, elijah reyen wrote:
> > > Does rsync has directory name length limit? I was
> > > trying to rsync a directory that has the name length of
> > > 34 characters and getting permission denied error.
> > >
> > > $ rsync -avz --delete --force -e ssh
> > > /usr/local/apache/htdocs 192.168.0.2:/usr/local/apache
> > > building file list ... readlink
> > > htdocs/CorporateLegalTimesEDITORIAL_files/cBug_blueXs.gif:
> > > Permission denied readlink
> > > httpd/html/CorporateLegalTimesEDITORIAL_files/title_a.gif:
> > > Permission denied
> > >
> > > When I rename the directory to about half of its
> > > original length, the error goes away. Any advise are
> > > appreciated.
>
> You aren't hitting an rsync limit. The only limit existing
> in rsync is MAXPATHLEN which if not defined by the libs will
> be 1024.
>
> Whatever is doing it seems to have a bug in any case.
> readlink or stat should return set errno to ENOENT,
> ENAMETOOLONG, or ENOTDIR depending on what is actually
> causing the error. EACCESS means the file is there and the
> path is good, you just don't have permission.
>
> Most likely it is the libraries causing the problem.
>
> In addition to the OS and rsync version question, what are
> the filesystem types?
>
>
>
> --
>
> J.W. SchultzPegasystems Technologies
> email address: [EMAIL PROTECTED]
>
> Remember Cernan and Schmitt
> --
> To unsubscribe or change options: http://lists.samba.org/mailman/listinfo/rsync
> Before posting, read: http://www.tuxedo.org/~esr/faqs/smart-questions.html
Re: Help With Restoring
> rsync --delete --stats --compress --recursive --times --perms --links > --rsh=/usr/bin/ssh --exclude "tmp/" --exclude "dev/" --exclude "proc/" > --exclude "backups/ " --delete-excluded --backup > --backup-dir=/backup2/BACKED_UP_SERVER_FQDN/$DAY -a /* > CENTRAL_SERVER_IP:/backup2/BACKED_UP_SERVER_FQDN/current && echo "Daily > backup ran on `date`" >> /var/log/backup.log Notice that if you have any dotfiles in / (that is, flies that begin with a "."), this will not copy them, but normally you wouldn't have dotfiles in / so it shouldn't matter. Might want to start using / instead of /* from now on though, just for good form. > This has been working fine and I've even been able to restore files using > scp from time to time. now I'm faced with a bare metal recovery cause of a > botched upgrade from Redhat 7.1 to 8.0 that failed half way through. This > machine was still accessible via console and ssh (putty). I signed in via > ssh and ran... > > # cd / > # scp -r CENTRAL_SERVER_IP:/backup1/BACKED_UP_SERVER_FQDN/current/.* . > > This was running for a while and then i lost my connection and cant > reconnect. I won't have console access till the morning but any advice > would be greatly appreciated. Don't you mean: scp -rp CENTRAL_SERVER_IP:/backup1/BACKED_UP_SERVER_FQDN/current/. . ? The command you list above won't copy anything, since there are no dotfiles in the root directory. Also, you have backup2 in the rsync command and backup1 in the scp command. Maybe that was just a typo though... One final thought. Sometimes scp has issues with symlinks (as in, copying the target instead of the link). Might want to use: cd / rsync -av CENTRAL_SERVER_IP:/backup1/BACKED_UP_SERVER_FQDN/current/ . Mike -- To unsubscribe or change options: http://lists.samba.org/mailman/listinfo/rsync Before posting, read: http://www.tuxedo.org/~esr/faqs/smart-questions.html
Re: [PATCH] Add .svn to the exclude list for --cvs-exclude
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 trailing slashes would be interpreted correctly, and then tested a modified version to ensure proper functioning. This is a simple enough change that I went ahead and checked it into CVS. In my version I added the ".svn/" pattern near the other dirs instead of at the end of the list. Thanks, Jon, for the patch. ..wayne.. -- To unsubscribe or change options: http://lists.samba.org/mailman/listinfo/rsync Before posting, read: http://www.tuxedo.org/~esr/faqs/smart-questions.html
Re: Help With Restoring
> > rsync --delete --stats --compress --recursive --times --perms --links > > --rsh=/usr/bin/ssh --exclude "tmp/" --exclude "dev/" --exclude "proc/" > > --exclude "backups/ " --delete-excluded --backup > > --backup-dir=/backup2/BACKED_UP_SERVER_FQDN/$DAY -a /* > > CENTRAL_SERVER_IP:/backup2/BACKED_UP_SERVER_FQDN/current && echo "Daily > > backup ran on `date`" >> /var/log/backup.log > > Notice that if you have any dotfiles in / (that is, flies that begin with > a "."), this will not copy them, but normally you wouldn't have dotfiles > in / so it shouldn't matter. Might want to start using / instead of /* > from now on though, just for good form. Thanks fot the tip :) > > > This has been working fine and I've even been able to restore files using > > scp from time to time. now I'm faced with a bare metal recovery cause of a > > botched upgrade from Redhat 7.1 to 8.0 that failed half way through. This > > machine was still accessible via console and ssh (putty). I signed in via > > ssh and ran... > > > > # cd / > > # scp -r CENTRAL_SERVER_IP:/backup1/BACKED_UP_SERVER_FQDN/current/.* . > > > > This was running for a while and then i lost my connection and cant > > reconnect. I won't have console access till the morning but any advice > > would be greatly appreciated. > > Don't you mean: > > scp -rp CENTRAL_SERVER_IP:/backup1/BACKED_UP_SERVER_FQDN/current/. . > > ? > > The command you list above won't copy anything, since there are no > dotfiles in the root directory. Also, you have backup2 in the rsync > command and backup1 in the scp command. > > Maybe that was just a typo though... As never having restored anything more that a few files at a time as the Linux newbie that I am, I'm sure i was off. Thanks for the tip again :) Typo it was. Should have been backup2 in the scp command. > > One final thought. Sometimes scp has issues with symlinks (as in, copying > the target instead of the link). Might want to use: > > cd / > rsync -av CENTRAL_SERVER_IP:/backup1/BACKED_UP_SERVER_FQDN/current/ . I will try this first thing in the morning when I have console access. Just one more thing; Based on the script I use, am I SOL or with a little elbow greese in the morning get my server back? Thank you for your time and advice. I really appreciate it! Mark > > Mike > > -- > To unsubscribe or change options: http://lists.samba. > org/mailman/listinfo/rsync > Before posting, read: http://www.tuxedo.org/~esr/faqs/smart-questions.html
Replaced file?
Title: Message Hello - I'm wondering if there is a way around this particular issue? I backup a database into a dump file. I backup this file using rsync. I then make a few minor changes in the database and then create another dump file. I then backup with rsync. Instead of merely backing up the incremental changes, it backs up the entire file. I'm sure this is due to the fact that the creation of the dump file doesn't really modify or update the file, but overwrites with a new file. However, the fact remains that there are only a few changes to the dump file. Is there anyway around this? Is there some way to make rsync think this is the same file? How does rsync know this is indeed a different file? Thanks - Max
Re: Help With Restoring
Using rsync on to restore / might be OK because it creates copies and then renames but in general it is a bad idea to try to restore / in-place. Better to boot from other media, mount root &c on another tree and then restore there. On Wed, Jan 08, 2003 at 11:20:09PM -0500, [EMAIL PROTECTED] wrote: > > > rsync --delete --stats --compress --recursive --times --perms --links > > > --rsh=/usr/bin/ssh --exclude "tmp/" --exclude "dev/" --exclude "proc/" > > > > --exclude "backups/ " --delete-excluded --backup > > > --backup-dir=/backup2/BACKED_UP_SERVER_FQDN/$DAY -a /* > > > CENTRAL_SERVER_IP:/backup2/BACKED_UP_SERVER_FQDN/current && echo > "Daily > > > backup ran on `date`" >> /var/log/backup.log > > > > Notice that if you have any dotfiles in / (that is, flies that begin > with > > a "."), this will not copy them, but normally you wouldn't have dotfiles > > in / so it shouldn't matter. Might want to start using / instead of /* > > from now on though, just for good form. > > > Thanks fot the tip :) > > > > > > > This has been working fine and I've even been able to restore files > using > > > scp from time to time. now I'm faced with a bare metal recovery cause > of a > > > botched upgrade from Redhat 7.1 to 8.0 that failed half way through. > This > > > machine was still accessible via console and ssh (putty). I signed in > via > > > ssh and ran... > > > > > > # cd / > > > # scp -r CENTRAL_SERVER_IP:/backup1/BACKED_UP_SERVER_FQDN/current/.* . > > > > > > > This was running for a while and then i lost my connection and cant > > > reconnect. I won't have console access till the morning but any advice > > > > would be greatly appreciated. > > > > Don't you mean: > > > > scp -rp CENTRAL_SERVER_IP:/backup1/BACKED_UP_SERVER_FQDN/current/. . > > > > ? > > > > The command you list above won't copy anything, since there are no > > dotfiles in the root directory. Also, you have backup2 in the rsync > > command and backup1 in the scp command. > > > > Maybe that was just a typo though... > > > As never having restored anything more that a few files at a time as the > Linux newbie that I am, I'm sure i was off. Thanks for the tip again :) > Typo it was. Should have been backup2 in the scp command. > > > > > > One final thought. Sometimes scp has issues with symlinks (as in, > copying > > the target instead of the link). Might want to use: > > > > cd / > > rsync -av CENTRAL_SERVER_IP:/backup1/BACKED_UP_SERVER_FQDN/current/ . > > > I will try this first thing in the morning when I have console access. > > Just one more thing; Based on the script I use, am I SOL or with a little > elbow greese in the morning get my server back? > > > Thank you for your time and advice. I really appreciate it! > > Mark > > > > > Mike > > > > -- > > To unsubscribe or change options: http://lists.samba. > > org/mailman/listinfo/rsync > > Before posting, read: > http://www.tuxedo.org/~esr/faqs/smart-questions.html -- J.W. SchultzPegasystems Technologies email address: [EMAIL PROTECTED] Remember Cernan and Schmitt -- To unsubscribe or change options: http://lists.samba.org/mailman/listinfo/rsync Before posting, read: http://www.tuxedo.org/~esr/faqs/smart-questions.html
--exclude and --delete-exclude problem
Hi. I'm trying to accomplish the following ; 1) First, I did a rsync for a file, like this /usr/bin/rsync -lptgoD --delete --rsh=/usr/bin/ssh -R --delete-excluded -vv [EMAIL PROTECTED]:/usr/local/src/* /tmp/localhost/daily.0 If I did a ls -la to the destination dir (/tmp/localhost/daily.0/usr/local/src/README) I take ls -la /tmp/localhost/daily.0/usr/local/src/ total 60 drwxrwsr-x2 root staff4096 Jan 9 00:43 . drwxrwsr-x3 root staff4096 Jan 6 23:31 .. -rw-r--r--5 root staff 10377 Jan 9 00:43 README Later, when I make the following rsync /usr/bin/rsync -lptgoD --delete --rsh=/usr/bin/ssh -R --delete-excluded -vv --exclude=/usr/local/src/README* [EMAIL PROTECTED]:/usr/local/src/* /tmp/localhost/daily.0 I see that the README file stills exists. If I make the same process for a direcory, for example /usr/local/src/temp/ , it works fine, rsync delete the /usr/local/src/temp directory, and all it's contents. I see that the problem appears when I have a file on the target. Here a verbose output (-v) cmolina:/home/cmolina/projects/pdbs# /usr/bin/rsync -lptgoD --delete --rsh=/usr/bin/ssh -R --delete-excluded -v --exclude=/usr/local/src/README [EMAIL PROTECTED]:/usr/local/src/* /tmp/localhost/daily.0 add_exclude(/usr/local/src/README,exclude) cmd=/usr/bin/ssh machine=127.0.0.1 user=root path=/usr/local/src/* cmd=/usr/bin/ssh -l root 127.0.0.1 rsync --server --sender -vlogDtpR --delete-excluded . /usr/local/src/* opening connection using /usr/bin/ssh -l root 127.0.0.1 rsync --server --sender -vlogDtpR --delete-excluded . "/usr/local/src/*" [EMAIL PROTECTED]'s password: add_exclude(/usr/local/src/README,exclude) server_sender starting pid=11625 make_file(1,/usr) expand file_list to 4000 bytes, did move recv_file_name(/usr) make_file(1,/usr/local) recv_file_name(/usr/local) make_file(1,/usr/local/src) recv_file_name(/usr/local/src) excluding file /usr/local/src/README because of pattern /usr/local/src/README skipping directory /usr/local/src/rsback-0.4.2 make_file(1,/usr/local/src/rsback-0.4.2.tar.gz) recv_file_name(/usr/local/src/rsback-0.4.2.tar.gz) received 4 names [11621] i=0 usr mode=040755 len=4096 [11621] i=1 usr local mode=042775 len=4096 [11621] i=2 usr/local src mode=042775 len=4096 [11621] i=3 usr/local/src rsback-0.4.2.tar.gz mode=0100600 len=39192 [11625] i=0 usr mode=040755 len=4096 [11625] i=1 /usr local mode=042775 len=4096 [11625] i=2 /usr/local src mode=042775 len=4096 [11625] i=3 /usr/local/src rsback-0.4.2.tar.gz mode=0100600 len=39192 recv_file_list done get_local_name count=4 /tmp/localhost/daily.0 recv_files(4) starting send_file_list done send_files starting generator starting pid=11621 count=4 recv_generator(usr,0) recv_generator(usr/local,1) recv_generator(usr/local/src,2) recv_generator(usr/local/src/rsback-0.4.2.tar.gz,3) usr/local/src/rsback-0.4.2.tar.gz is uptodate generate_files phase=1 recv_files phase=1 send_files phase=1 generate_files phase=2 send files finished total: matches=0 tag_hits=0 false_alarms=0 data=0 recv_generator(usr,0) recv_generator(usr/local,1) recv_generator(usr/local/src,2) recv_files finished wrote 41 bytes read 895 bytes 267.43 bytes/sec total size is 39192 speedup is 41.87 client_run2 waiting on 11622 _exit_cleanup(code=0, file=main.c, line=925): entered _exit_cleanup(code=0, file=main.c, line=925): about to call exit(0) cmolina:/home/cmolina/projects/pdbs# ls -la /tmp/localhost/daily.0/usr/local/src/ total 60 drwxrwsr-x2 root staff4096 Jan 9 00:43 . drwxrwsr-x3 root staff4096 Jan 6 23:31 .. -rw-r--r--5 root staff 10377 Jan 9 00:43 README -rw---1 root staff 39192 Nov 27 21:56 rsback-0.4.2.tar.gz Thanks in advance. Carlos -- To unsubscribe or change options: http://lists.samba.org/mailman/listinfo/rsync Before posting, read: http://www.tuxedo.org/~esr/faqs/smart-questions.html
Re: [PATCH] Add .svn to the exclude list for --cvs-exclude
On Thu, Jan 09, 2003 at 12:25:29AM +, Jon Middleton wrote: > On Wed, Jan 08, 2003 at 04:00:23PM -0800, jw schultz wrote: > > On Wed, Jan 08, 2003 at 11:24:03PM +, Jon Middleton wrote: > > > > > > The attached patch adds the Subversion adm directory (.svn) to the > > > list of excludes for the --cvs-exclude option and also updates the man > > > page. > > > I wonder if it shouldn't be ".svn/". > > I also don't care much for the inconstistant puctuation. > > It could be ".svn/", but I just added it in the same format as the > other entries in the list. My comment was as much for the maintainders as you. - "RCS","SCCS","CVS","CVS.adm","RCSLOG","cvslog.*", + "RCS/", "SCCS/", "CVS/", "CVS.adm", "RCSLOG", "cvslog.*", Might be worth doing to tighten the patterns. > > > Is the .svn directory the only addition appropriate for > > subversion? No new file prefixes or suffixes from update > > conflicts? > > Subversion creates the following files durning a conflicted update > > *.mine > *.rOLDREV > *.rNEWREV > > where OLDREV and NEWREV are the version number of that file in the > repository, but I think they are a bit too generic to be excluded. > > > Also, it is the rsync.yo file that needs updating. rsync.1 > > is derived via yodl. > > I've attached a updated patch attached. Very good. We'll see if anything comes of it. > > -- > Jon > > "First things first -- but not necessarily in that order" > -- The Doctor, "Doctor Who" > diff -Nur -x 'debian*' -x shconfig -x '*~' rsync-2.5.5/exclude.c >rsync-2.5.5-modified/exclude.c > --- rsync-2.5.5/exclude.c 2002-02-18 19:10:28.0 + > +++ rsync-2.5.5-modified/exclude.c2003-01-08 22:41:10.0 + > @@ -390,7 +390,7 @@ >"tags","TAGS",".make.state",".nse_depinfo", >"*~", "#*", ".#*", ",*", "*.old", "*.bak", "*.BAK", "*.orig", >"*.rej", ".del-*", "*.a", "*.o", "*.obj", "*.so", "*.Z", "*.elc", "*.ln", > - "core",NULL}; > + "core", ".svn",NULL}; > > > > diff -Nur -x 'debian*' -x shconfig -x '*~' rsync-2.5.5/rsync.yo >rsync-2.5.5-modified/rsync.yo > --- rsync-2.5.5/rsync.yo 2002-02-06 21:20:49.0 + > +++ rsync-2.5.5-modified/rsync.yo 2003-01-09 00:05:31.0 + > @@ -551,7 +551,7 @@ > > quote(RCS SCCS CVS CVS.adm RCSLOG cvslog.* tags TAGS .make.state > .nse_depinfo *~ #* .#* ,* *.old *.bak *.BAK *.orig *.rej .del-* > -*.a *.o *.obj *.so *.Z *.elc *.ln core) > +*.a *.o *.obj *.so *.Z *.elc *.ln core .svn) > > then files listed in a $HOME/.cvsignore are added to the list and any > files listed in the CVSIGNORE environment variable (space delimited). -- J.W. SchultzPegasystems Technologies email address: [EMAIL PROTECTED] Remember Cernan and Schmitt -- To unsubscribe or change options: http://lists.samba.org/mailman/listinfo/rsync Before posting, read: http://www.tuxedo.org/~esr/faqs/smart-questions.html
