dup error of rsync 3.0.6-1 under cygwin 1.7.0-62 and 63
I have used earlier rsync on cygwin successfully for a long. I have now moved to cygwin 1.7.0, which required moving to rsync 3.0.6-1 at the same time. (The -1 is for minor cygwin-specific patches.) When I do almost any command with rsync, such as the one below, it breaks at a dup2 after a fork in pipe.c (routine piped_child). Windows gives error code 6, which is translated by cygwin to errno 9 = EBADF, and rsync then terminates. rsync -avzuP foo roc:talks/ Even rsync -r . fails the same way, though it does not need a network connection. Steven Monai suggests that the problem may be a mismatch in protocol (30 versus 29), though I think the last command scuttles that possibility. I think it has something to do with cygwin, since cygwin 1.5 seemed ok, but it could be a combination of changes un rsync and cygwin ... Best wishes -- Eliot Moss == J. Eliot B. Moss, Professor http://www.cs.umass.edu/~mosswww Director, Arch. and Lang. Impl. Lab. +1-413-545-4206voice Department of Computer Science+1-413-695-4226 cell 140 Governor's Drive, Room 372+1-413-545-1249 fax University of Massachusetts at Amherstm...@cs.umass.edu email Amherst, MA 01003-9264 USA +1-413-545-2746 Laurie Downey sec'y == -- Please use reply-all for most replies to avoid omitting the mailing list. To unsubscribe or change options: https://lists.samba.org/mailman/listinfo/rsync Before posting, read: http://www.catb.org/~esr/faqs/smart-questions.html
Re: dup error of rsync 3.0.6-1 under cygwin 1.7.0-62 and 63
Eliot Moss wrote: I have used earlier rsync on cygwin successfully for a long. I have now moved to cygwin 1.7.0, which required moving to rsync 3.0.6-1 at the same time. (The -1 is for minor cygwin-specific patches.) When I do almost any command with rsync, such as the one below, it breaks at a dup2 after a fork in pipe.c (routine piped_child). Windows gives error code 6, which is translated by cygwin to errno 9 = EBADF, and rsync then terminates. rsync -avzuP foo roc:talks/ Even rsync -r . fails the same way, though it does not need a network connection. Steven Monai suggests that the problem may be a mismatch in protocol (30 versus 29), though I think the last command scuttles that possibility. I think it has something to do with cygwin, since cygwin 1.5 seemed ok, but it could be a combination of changes un rsync and cygwin ... Thought I'd give the rsync HEAD a try on this, since it does include changes in the I/O part of the world. It fails in exactly the same way ... (but in io.c, of course). Cheers -- Eliot -- Please use reply-all for most replies to avoid omitting the mailing list. To unsubscribe or change options: https://lists.samba.org/mailman/listinfo/rsync Before posting, read: http://www.catb.org/~esr/faqs/smart-questions.html
Re: Take2: rsync over ssh with --link-dest
Hi, Overriding the server command line is generally a bad idea for the reasons you went on to note. Instead, use an rsync daemon. You can even have the daemon invoked over ssh with a forced command, see: https://bugzilla.samba.org/show_bug.cgi?id=4163#c4 That looks like the way to go. I've got it set up and running for a few days now, and it's working okay. I'm a bit disappointed that I can't do it by overriding the server command line, but it's okay. Thanks again, Alex -- Please use reply-all for most replies to avoid omitting the mailing list. To unsubscribe or change options: https://lists.samba.org/mailman/listinfo/rsync Before posting, read: http://www.catb.org/~esr/faqs/smart-questions.html
Re: Take2: rsync over ssh with --link-dest
I'm a bit disappointed that I can't do it by overriding the server command line Why? Does it have some advantage over the use of an rsync daemon (I can't imagine what)? One can't really expect overriding the server arguments not to lead to the inconsistent behavior you saw. Simplicity. I'd like to be able to have the server side feed me all data beginning with the path I specify, such /backup/serverA, and have the client side be able to --include=/usr/bin to be able to 'download' only the data from /backup/serverA/usr/bin and exclude everything else. Instead, I have about eight sections of my rsyncd.conf to do this; one for each directory tree that I want to back up to a different location, primarily based on dates, to have multiple incrementals. Thanks, Alex -- Please use reply-all for most replies to avoid omitting the mailing list. To unsubscribe or change options: https://lists.samba.org/mailman/listinfo/rsync Before posting, read: http://www.catb.org/~esr/faqs/smart-questions.html
Re: Take2: rsync over ssh with --link-dest
On Mon, 2009-11-09 at 00:28 -0500, Alex wrote: I'm a bit disappointed that I can't do it by overriding the server command line Why? Does it have some advantage over the use of an rsync daemon (I can't imagine what)? One can't really expect overriding the server arguments not to lead to the inconsistent behavior you saw. Simplicity. I'd like to be able to have the server side feed me all data beginning with the path I specify, such /backup/serverA, In other words, you were specifying a bogus source path and counting on sshd to override it with the real one. Clever. I didn't catch that the first time. Realize that the ability to set a module's path in the rsyncd.conf file and have the client refer to the module by a well-known name gives you the same functionality, and actually more, because the client can specify a subdirectory path within the module. and have the client side be able to --include=/usr/bin to be able to 'download' only the data from /backup/serverA/usr/bin and exclude everything else. That --include means exclude everything else is a common misconception; see the man page. But I imagine the issue will become moot if you have the client specify a subdirectory of the module instead of using filters. Instead, I have about eight sections of my rsyncd.conf to do this; one for each directory tree that I want to back up to a different location, primarily based on dates, to have multiple incrementals. If the daemon solution is looking fundamentally more complicated than the set of forced server commands you previously had, you're probably going about it the wrong way and I could help if you post the rsyncd.conf file. -- Matt -- Please use reply-all for most replies to avoid omitting the mailing list. To unsubscribe or change options: https://lists.samba.org/mailman/listinfo/rsync Before posting, read: http://www.catb.org/~esr/faqs/smart-questions.html
Re: Yet another include/exclude question
What if I also want to include everything in /this_dir/ without running two instances and still being able to use --delete? I thought --include=/this_dir/ --include=/this_dir/*** would do it, but it doesn't. The exclude * seems to overwrite the include matches: [sender] hiding file this_dir/foo because of pattern * Tom Steven Monai wrote: Tony wrote: On Nov 6, 2009, at 12:43 AM, Thomas Gutzler wrote: Hi, How can I include only *.foo and *.bar files in an rsync? To make it a bit more difficult: Those files can be anywhere in the directory structure. I've been reading and trying for a while but the best I got is all *.foo and *.bar files in ./ but none of the ones inside any directories. There is an example in the man pages for *.c files that will do what you want. Try: --include=*/ --include=*.foo --exclude=* Yes. I would also strongly recommend the section of the man page that describes --prune-empty-dirs. Cheers, -SM -- -- Please use reply-all for most replies to avoid omitting the mailing list. To unsubscribe or change options: https://lists.samba.org/mailman/listinfo/rsync Before posting, read: http://www.catb.org/~esr/faqs/smart-questions.html
[SCM] The rsync repository. branch, master, updated. v3.0.3-270-gf397616
This is an automated email from the git hooks/post-receive script. It was generated because a ref change was pushed to the repository containing the project The rsync repository.. The branch, master has been updated via f397616e00afb4e9fb42709dfaf270e10fac90fa (commit) via 4351c039adf4f6c3d062233079179ca01d24b43c (commit) via 304d7b5817d6e1d3cf59b9edae2213433d901cdc (commit) via 9270e88d76d3ea9e94d48977fbea57b997545577 (commit) from 2907af472d1f33b3c422cb9f601c121b242aa9c7 (commit) Those revisions listed above that are new to this repository have not appeared on any other notification email; so we list those revisions in full, below. - Log - commit f397616e00afb4e9fb42709dfaf270e10fac90fa Author: Wayne Davison way...@samba.org Date: Sun Nov 8 11:51:02 2009 -0800 Change an RERR_* to RERR_FILEIO. commit 4351c039adf4f6c3d062233079179ca01d24b43c Author: Wayne Davison way...@samba.org Date: Sun Nov 8 11:50:43 2009 -0800 Mention who got the unknown logcode. commit 304d7b5817d6e1d3cf59b9edae2213433d901cdc Author: Wayne Davison way...@samba.org Date: Sun Nov 8 11:43:16 2009 -0800 More improvements for abnormal exits. commit 9270e88d76d3ea9e94d48977fbea57b997545577 Author: Wayne Davison way...@samba.org Date: Sun Nov 8 00:12:33 2009 -0800 Save first filename and linenum in case exit_cleanup() recurses. --- Summary of changes: cleanup.c | 35 +-- errcode.h |2 -- io.c | 29 - log.c |3 +-- rsync.h |2 +- sender.c |2 +- 6 files changed, 44 insertions(+), 29 deletions(-) hooks/post-receive -- The rsync repository. ___ rsync-cvs mailing list rsync-cvs@lists.samba.org https://lists.samba.org/mailman/listinfo/rsync-cvs
[SCM] The rsync repository. branch, master, updated. v3.0.3-271-gcece2e3
This is an automated email from the git hooks/post-receive script. It was generated because a ref change was pushed to the repository containing the project The rsync repository.. The branch, master has been updated via cece2e3f5e335b8d1bd0862dbc9edbf2d5a4f5dd (commit) from f397616e00afb4e9fb42709dfaf270e10fac90fa (commit) Those revisions listed above that are new to this repository have not appeared on any other notification email; so we list those revisions in full, below. - Log - commit cece2e3f5e335b8d1bd0862dbc9edbf2d5a4f5dd Author: Wayne Davison way...@samba.org Date: Sun Nov 8 20:17:02 2009 -0800 Make use of seteuid() determined by configure. --- Summary of changes: clientserver.c |6 +- configure.in |2 +- 2 files changed, 6 insertions(+), 2 deletions(-) hooks/post-receive -- The rsync repository. ___ rsync-cvs mailing list rsync-cvs@lists.samba.org https://lists.samba.org/mailman/listinfo/rsync-cvs
