https://qa.mandrakesoft.com/show_bug.cgi?id=2042
------- Additional Comments From [EMAIL PROTECTED] 2003-02-22 05:00 ------- That's faulty logic, David. Where the problem is that a piece of software handles sucky mirrors badly, there are two possible solutions: 1. Somehow ensure there are never any sucky mirrors again ever. 2. Make the software handle sucky mirrors better. Your message implies the sensible solution is #1. It isn't. ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is. ------- Reminder: ------- assigned_to: [EMAIL PROTECTED] status: UNCONFIRMED creation_date: description: >From a terminal, su to root and start mcc. Go to software management->mandrake >update. It starts searching for updates and these messages appear on the terminal: --10:10:08-- ftp://carroll.cac.psu.edu/pub/linux/distributions/mandrake/updates/9.0/base/hdlist.cz => `/var/cache/urpmi/partial/.listing' Resolving carroll.cac.psu.edu... done. Connecting to carroll.cac.psu.edu[128.118.2.96]:21... connected. Logging in as anonymous ... The server refuses login. Retrying. .................... --10:12:06-- ftp://carroll.cac.psu.edu/pub/linux/distributions/mandrake/updates/9.0/base/hdlist.cz (try:17) => `/var/cache/urpmi/partial/.listing' Connecting to carroll.cac.psu.edu[128.118.2.96]:21... connected. Logging in as anonymous ... The server refuses login. Retrying. 1) As can be seen, it tried to connect 17 times (over a period of 2 minutes). There is no option in mcc to set a limit to the number of connection attempts. 2) Whats as bad as 1) is that the pop up window which asks to start searching for updates, goes blank when the update search is on. This means, even it had a button "stop search now" it will not be visible. In other words, there is no way to stop this search. Killing mcc is the only way.
