[
https://issues.apache.org/jira/browse/SSHD-120?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Guillaume Nodet resolved SSHD-120.
----------------------------------
Resolution: Fixed
Fix Version/s: 0.7.0
Assignee: Guillaume Nodet
Thx for the patch Otto.
I've reworked it a bit to minimize the number of packets send by filling the
buffer up to a certain point instead of limiting the number of files sent.
> list 1500 files in one directory not working for mindterm sftp client
> ---------------------------------------------------------------------
>
> Key: SSHD-120
> URL: https://issues.apache.org/jira/browse/SSHD-120
> Project: MINA SSHD
> Issue Type: Bug
> Affects Versions: 0.5.0
> Environment: windows xp professional sun jre 1.5
> windows 2003 server sun jre 1.5
> mindterm 3.4 ftp2sftp
> Reporter: Otto Frost
> Assignee: Guillaume Nodet
> Fix For: 0.7.0
>
> Attachments: sftpsubsystem.diff
>
> Original Estimate: 168h
> Remaining Estimate: 168h
>
> mindterm is used in ftp2sftp mode
> trying to list files in a directory "manyfiles" with > 1500 files doesn't
> work on the "apache mina sshd"
> when doing the following operation it doesn't work. In the "manyfiles" dir
> there are >1500 files.
> mindterm can list files in a directory with < 50 files
> mindterm can list files on a opensshd server with a directory with > 1500
> files, therefore we think the error is in the "apache mina sshd" and not in
> mindterm, at least there is some incompatibility...
> ftp> o localhost 2120
> Connected to WKE198515.u-dom1.u-ssi.net.
> 220 FTPToSFTPProxy use 'ssh2-user@ssh2-host[:port]' as your username or
> ;ssh2-us
> er;keyfile;10@ssh2-host[:port]
> User (WKE198515.u-dom1.u-ssi.net:(none)): a@localhost:2222
> 331 Password required for a@localhost:2222.
> Password:
> 230 User a@localhost:2222 logged in.
> ftp> cd ../../../tst/manyfiles
> 250 CWD command successful.
> ftp> ls
> 200 PORT command successful.
> 150 Opening ASCII mode data connection for nlst.
> Connection closed by remote host.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
