https://bugzilla.samba.org/show_bug.cgi?id=1476
--- Additional Comments From [EMAIL PROTECTED] 2005-02-26 14:52 ---
(In reply to comment #13)
> I may be able to reproduce the original situation.
The original situation is a timeout at the end of all transferred data, not in
the middle
On Sat, Feb 26, 2005 at 04:34:32AM -0600, chris allen wrote:
> rsync works fine except it keeps asking for a password.
Just to be clear: rsync isn't asking for the password, ssh is. I'd
recommend testing a simpler ssh command until you get it working without
a password, and then use that setup t
https://bugzilla.samba.org/show_bug.cgi?id=1476
--- Additional Comments From [EMAIL PROTECTED] 2005-02-26 14:12 ---
I may be able to reproduce the original situation.
I can have a browser and X that are running with 90% load on
CPU 1 and 98% load on CPU 2. Once I have waited for the
https://bugzilla.samba.org/show_bug.cgi?id=1476
[EMAIL PROTECTED] changed:
What|Removed |Added
Status|ASSIGNED|RESOLVED
Resolution|
https://bugzilla.samba.org/show_bug.cgi?id=1889
[EMAIL PROTECTED] changed:
What|Removed |Added
Status|ASSIGNED|RESOLVED
Resolution|
I have a main server that I want to backup to my backup server. I don't
know on witch side that I need to make a key on
the code is bellow is what I am using
rsync -e "ssh -i /root/.ssh/rsync-key" -avHRrz --numeric-ids
--progress --stats --delete --exclude=/proc/* --exclude=/tmp/*
--exclu
https://bugzilla.samba.org/show_bug.cgi?id=1476
--- Additional Comments From [EMAIL PROTECTED] 2005-02-26 01:26 ---
I believe that using this "no-op" packet effectively implements the "keep alive"
option requested in bug 1889 without requiring an explicit option be given.
Nice.
I'm
