From: david-sarah Date: Sat, 8 Jan 2011 06:10:38 +0000 (-0800) Subject: docs/FTP-and-SFTP.rst: document issue in ref #1297. Remove known issue #1045 which... X-Git-Tag: allmydata-tahoe-1.8.2b1~79 X-Git-Url: https://git.rkrishnan.org/vdrive/%22news.html/frontends/specifications/install.html?a=commitdiff_plain;h=2b5b285dab9ace8e8f73c10445762a4c26e5613b;p=tahoe-lafs%2Ftahoe-lafs.git docs/FTP-and-SFTP.rst: document issue in ref #1297. Remove known issue #1045 which is fixed. Also some cosmetic changes. --- diff --git a/docs/frontends/FTP-and-SFTP.rst b/docs/frontends/FTP-and-SFTP.rst index ce17896b..93c62121 100644 --- a/docs/frontends/FTP-and-SFTP.rst +++ b/docs/frontends/FTP-and-SFTP.rst @@ -162,7 +162,7 @@ isn't very useful except for testing. For further information on SFTP compatibility and known issues with various clients and with the sshfs filesystem, see -http://tahoe-lafs.org/trac/tahoe-lafs/wiki/SftpFrontend . +``_. Dependencies ============ @@ -225,8 +225,8 @@ containing mutable files cannot even be listed over FTP. The FTP frontend sometimes fails to report errors, for example if an upload fails because it does meet the "servers of happiness" threshold (`ticket #1081 -`_). Upload errors also may not -be reported when writing files using SFTP via sshfs (`ticket #1059 +`_). Upload errors also +may not be reported when writing files using SFTP via sshfs (`ticket #1059 `_). Non-ASCII filenames are not supported by FTP (`ticket #682 @@ -234,8 +234,11 @@ Non-ASCII filenames are not supported by FTP (`ticket #682 with SFTP only if the client encodes filenames as UTF-8 (`ticket #1089 `_). -The gateway node may incur a memory leak when accessing many files via SFTP -(`ticket #1045 `_). +The gateway node may hang or consume 100% CPU if the client tries to rekey. +(`ticket #1297 `_). +This is due to `a bug in Twisted `_ +up to and including version 10.2. -For other known issues in SFTP, see -. +For options to disable rekeying in various clients in order to work around +this issue, and for other known issues in SFTP, see +``_.