Hello,
sometimes when transferring large files (has only
happened with downloads to me so far) the download
after a while (usually days) "stalls"; the status line
says "stalled" and the bits stop travelling.
I can't exactly tell whether the stall-situation is
caused by yafc
but I rather assume it's caused by a temporary outage
of my DSL connection.
However what I'd like to see on such an occassion is a
timeout and auto_reconnect by yafc. Unfornationally the
stall-situation appears not to be handled at all so
when a download stalls yafc will hang around _forever_
and not move on without manual intervention.
I'd be glad if this could be fixed since I really like
yafc.
I switched from lftp in favor of the better tag-list
handling and verbosity and except for this one issue
(and sometimes a segfault on program-exit which hasn't
really bothered me yet, tho) it works like a charme.
best regards
Logged In: YES
user_id=353210
If your concern is just that you are dropping a few packets
-- this should already be handled. At the kernel level, in
TCP, packet resends will occur. You shouldn't need to
reconnect at all (well, unless the outage is exceptionally
long -- much more than just a minute or two). As soon as a
timeout happens and a packet resend occurs, the transfer
should resume.
The only possibility I can think of off my head is that if
you have some sort of flaky NATing system that loses power
or resets itself (cheap Linksys "broadband router", for
instance). With something like this dying, it's *possible*
that TCP connections will get eaten alive.
I'm curious as to whether this only happens with yafc and
not lftp (i.e. it's not something that recently started
being caused by the environment rather than the FTP program).