|
|
cURL Mailing List Monthly Index Single Mail
curl-tracker mailing list Archives
[ curl-Bugs-1822405 ] curlftpfs hangs after reading files with no write permission
From: SourceForge.net <noreply_at_sourceforge.net>
Date: Tue, 30 Oct 2007 02:06:35 -0700
Bugs item #1822405, was opened at 2007-10-29 23:27
Please note that this message will contain a full copy of the comment thread,
Initial Comment:
http://sourceforge.net/tracker/index.php?func=detail&aid=1809225&group_id=160565&atid=816357
i'm not sure if this is really a libcurl problem, but there is a suspicion that libcurl doesn't move into a working state after reading a file failed (because no read permissions for the ftp user).
if there is a possibility to reproduce this bug without curlftpfs please tell me and i will try (perhaps a peace of demo code, which also uses curl_multi).
----------------------------------------------------------------------
>Comment By: Daniel Stenberg (bagder)
Message:
Since this doesn't seem to be a bug in libcurl...
----------------------------------------------------------------------
Comment By: n.f. (norbertf)
Message:
thanks a lot, i will try your test-case as soon as possible.
----------------------------------------------------------------------
Comment By: Dan Fandrich (dfandrich)
Message:
The error code from the FTP server in both cases is 550, so from libcurl's
----------------------------------------------------------------------
Comment By: n.f. (norbertf)
Message:
thanks, but i think that's not a file-not-found problem, but a
> RETR messages.4
have a look at curlftplog.txt, which i attached to the curlftpfs bug
after trying to read messages.4 and messages.3 (which both have no read
...
(hangs)
----------------------------------------------------------------------
Comment By: Dan Fandrich (dfandrich)
Message:
I've created test case 546 that tests a file-not-found FTP transfer
----------------------------------------------------------------------
Comment By: n.f. (norbertf)
Message:
sorry - the title of this bug report should be:
----------------------------------------------------------------------
You can respond by visiting:
These mail archives are generated by hypermail. |
Page updated November 12, 2010.
web site info