[Duplicity-tracker] [bug #25949] ncftp-failures

[Jan Kriesten]

Follow-up Comment #4, bug #25949 (project duplicity):


I found ncftp traces in the .ncftp directory which indicate that there's
really a timeout problem:

06:30:10  250: CWD command successful
06:30:10  > get -z duplicity-full-signatures.20090316T181457Z.sigtar.gpg
/tmp/duplicity-EHh43M-tempdir/mktemp-8JjSHW-3

06:30:10  Cmd: MLST duplicity-full-signatures.20090316T181457Z.sigtar.gpg
06:30:10  500: MLST not understood
06:30:10  Cmd: SIZE duplicity-full-signatures.20090316T181457Z.sigtar.gpg
06:30:10  213: 155453675
06:30:10  Cmd: MDTM duplicity-full-signatures.20090316T181457Z.sigtar.gpg
06:30:10  213: 20090316192354
06:30:10  Cmd: PORT 78,46,107,20,215,30
06:30:10  200: PORT command successful
06:30:10  Cmd: RETR duplicity-full-signatures.20090316T181457Z.sigtar.gpg
06:30:10  150: Opening BINARY mode data connection for
duplicity-full-signatures.20090316T181457Z.sigtar.gpg (155453675 bytes)
06:30:40  Starting abort sequence.
06:30:40  Cmd: ABOR

It's irritating to me that it's aborted when a file transfer is in progress.

Setting the timeout value higher solves the problem for the time being - but
only as long as the files doesn't grow bigger to take even longer to transfer
than that. Isn't there a better solution?


    _______________________________________________________

Reply to this item at:

  <http://savannah.nongnu.org/bugs/?25949>

_______________________________________________
  Nachricht geschickt von/durch Savannah
  http://savannah.nongnu.org/