On Tue, 17 Dec 2002, Chad Moss wrote: > I have used rsync on many systems, and never had a problem. I am > stumped on what to do with this. > I have a box behind a LinkSys router and I can not "push" or "pull" data > to or from it from anywhere.
Does it work for very small transfers? Does it work with --bwlimit set low enough so you never saturate your link? I can not rsync large amounts of data through my LinkSys without using the --bwlimit option. My LinkSys is doing NAT. I think it loses track of the address translation for the ssh connection under load. Then the ssh session just stops. I use --bwlimit=100, which is a third of the available bandwidth on the far end, and it just works. It's not a problem particular to rsync, other ssh sessions sometimes hang too. I just have more problems with rsync because I move more data that way. I always use "screen" for interactive sessions. > When I try, it logs into the remote server, gets the file list and just > stops. Could be a different problem, mine would often transfer quite a few files before stopping. > The remote server shows a process running until I control-c out of > it.when I do that, I get: > rsync error: received SIGUSR1 or SIGINT (code 20) at rsync.c(229) > rsync error: received SIGUSR1 or SIGINT (code 20) at main.c(785) > The command I am using is: > rsync -avz -e ssh [EMAIL PROTECTED]:/home > <mailto:[EMAIL PROTECTED]:/home%20/home/backup/servername/> > /home/backup/servername/ > I have forwarded ports 22 and 873 to that machine, and I have tried > putting it in the DMZ. > The results do not seem to change. > Thanks. -- Paulh -- To unsubscribe or change options: http://lists.samba.org/mailman/listinfo/rsync Before posting, read: http://www.tuxedo.org/~esr/faqs/smart-questions.html
