Hi,
We were just today making some promising tests
with F-Secure sshd2 v 3.0 and rsync 2.4.6
in OSF1 (Digital Unix).
The rsync+'ssh2 v2.0' server on OSF1
were hanging - but first small tests
did not any more show this trouble.
This hanging was most often totally
preventing using
On Mon, Sep 17, 2001 at 12:15:12PM -0600, [EMAIL PROTECTED] wrote:
Easy enough... look at your parameters. You're saying that you must not transfer
more than 48kb in a session... you actual mileage will be slightly smaller,
because of overhead. You have limited yourself to a bandwidth of
Carey,
What you are seeing is, in fact, the case, but the function that creates
the dirs is robust_move() in backup.c
The backup option captures files and/or directories that are deleted or
changed between syncs. So, if a directory is *changed*
(deleted/renamed/moved), then the directory *and*
On Thu, Sep 20, 2001 at 01:00:46AM +, M. Drew Streib wrote:
On Thu, Sep 20, 2001 at 10:47:15AM +1000, Cameron Simpson wrote:
That way we could do SMTP over SSL etc etc transparently: clients connect,
say SSL, if rejected either fall back or fall out, and if accepted
then away we all
On Thu, Sep 20, 2001 at 08:52:26AM -0500, Carey Jung wrote:
Not so.
--timeout=TIMEOUT
This option allows you to set a maximum IO timeout in
seconds. If no data is transferred for the specified
time then rsync will exit. The default is 0,
i meant to send this to the whole list... maybe someone else has seen it and can
figure out how to fix it.
Tim Conway
[EMAIL PROTECTED]
303.682.4917
Philips Semiconductor - Longmont TC
1880 Industrial Circle, Suite D
Longmont, CO 80501
Available via SameTime Connect within Philips
Available as
I'm not Dave Dykstra [[EMAIL PROTECTED]] writes:
On September 9 Tridge submitted a fix to CVS for that problem. See
revision 1.25 at
http://pserver.samba.org/cgi-bin/cvsweb/rsync/generator.c
I'm not sure that fixes the use of the timeout for the overall
process. See a recent answer by
