Version: 3.1.0 (using KDE 3.1.0) Installed from: Mandrake Linux Cooker i586 - Cooker Compiler: gcc version 3.2.2 (Mandrake Linux 9.1 3.2.2-3mdk) OS: Linux (i686) release 2.4.21-0.13mdk I open a window and connect to my sevice providers ftp server.(www.jirehmedia.com) then I close it at the end of the session. If I try to connect again after the server complains that I am already connected so I can't authenticate. It seems really weird. I can answer questions about it but I wouldn't know where to begin to diagnose the problem. I don't have problems with virgin.net's ftp though. John
My Konqueror version is from kde 3.1 from mandrakes 9.1 packages and upto date.
FYI, kio slaves *will* hang around awhile after that app that spawns them quits. I'm not sure exactly how long the "awhile" is though... Now, One would hope that opening another konq window to the same site would re-use the existing kio slave instead of launching a new one.
I seems that the kio_ftp isn't reused even if you open a new window while the old one is still there. This means that ftp sites that only allow one connection are a real pain to use. It must also affect performance on slow systems? I don't have a slow system to test though. Can kde be made to reuse kio slaves because this will affect your ability to save to websites from kword regularly etc. The reason there is no problem from virgin.net is that it accepts simultanious connections
*** Bug 60506 has been marked as a duplicate of this bug. ***
*** Bug 66690 has been marked as a duplicate of this bug. ***
Would it be possible to limit the number of simultanious connections to a site, preferably per site (just like you can accept or reject cookies per site)? If the number of connections is maxed out, further requests should be queued (not sure if I spelled that one right...) I fairly frequently run into problems relating to this.
*** This bug has been confirmed by popular vote. ***
Is this still an issue? ioslaves are always cached, but they will die off after a minute or two. Limiting the number of ioslaves per site is a wish that is not implemented and is not the issue of this bug report.
Unconfirming since I can't reproduce this.
Re-unconfirming.
*** Bug 141769 has been marked as a duplicate of this bug. ***
This bug is NOT RESOLVED, and is more or less making KDE (quanta, kate, otherwise very usefull apps...) useless as a platform for web development, if you are stuck with a hosting provider who enforces the 'max number of connections per client' restriction. This is a big bummer, and someone ought to fix this.
*** Bug 207191 has been marked as a duplicate of this bug. ***
Has there been any progress on this? I just ran into this issue myself, and it is very cumbersome to have to wait several minutes before you can open another file. I guess I can count myself lucky that my server allows up to 4 simultaneous connections. And why is this bug report still NEW when so many people have CONFIRMED it exists by voting and comments in this report and in reports marked as duplicates?
using dolphin and connecting with sftp, ftp to a server with a limitation of connections allways kicks me out after browsing through some folders. connecting with konquer .. the server never kicked me out. its realy stupid if you try to upload some stuff with no chance to browse into the target folder before kicked out by "Too many connections for this ip". I have these Problems sinse 1/2 year. Will it be fixed?
For this issue to be fixed someone needs to give an example server where the issue can be duplicated. It is difficult to troubleshoot something without actually being able to reproduce the problem. Anyhow, as of KDE 4.5 the limit on the number of connections allowed per server are honored. For example, for the ftp ioslave the number of maximum connections allowed per host are 2 and the total number ftp ioslaves that can be started is set to 10.[1] Additionally both dolphin and konqueror share the same file browser component, the dolphin part, and as such the issue in one should show up in the other. However, that makes no difference to this issue, since the problem is in how efficiently ioslaves (ftp/sftp) are recycled and used by the KIO scheduler. In the end, providing an example server that limits the number of connections it allows will go a long way on resolving this issue. Please do not expect developers to have the time to create such servers for themselves and run tests. [1] https://projects.kde.org/projects/kde/kdelibs/repository/revisions/master/entry/kioslave/ftp/ftp.protocol
I have set up an account on my shared hosting service to test this. I will give the account informations to any developper interested if they contact me by mail at pouletfou _at_ gmail.com
(In reply to comment #19) > I have set up an account on my shared hosting service to test this. > I will give the account informations to any developper interested if they > contact me by mail at pouletfou _at_ gmail.com You can send that information to my email address in this bug report...
Validated to work correctly using the test server provided by Poulet. The fix for this issue is as outlined in comment #18. Additionally there will be more fixes coming in KDE 4.7 that improve the reuse of already established connections to a server. See https://git.reviewboard.kde.org/r/101333/