Summary: | Mirrorselect 0.6 problems | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Narada Sage <narada.sage> |
Component: | Current packages | Assignee: | John Mylchreest (RETIRED) <johnm> |
Status: | RESOLVED FIXED | ||
Severity: | normal | ||
Priority: | High | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
Narada Sage
2003-07-25 04:05:08 UTC
for the record, I had this same problem even with 0.5 every once in a while. It seemed to happen when I was using a lot of my bandwidth up (not all of it, just enough to slow things down). Depending on and using netselect makes mirrorselect slower, bulkier and more error prone. Perhaps interactive mode should be the only mode of working. That will be faster, better distributed geographically and less likely to cause problems. Just a thought. automatic mode is an optional mode, and by no means is ideal. it does have a few drawbacks, although all problems I currently know about will have a fix in the next release of mirrorselect. They are nearly always related to routing, dns, or other similar problems. it should still return a list, and those errors imo arent whats stopping it, some routers prevent 40+ requests all at the samew time, so mirrorselect will in furture split it into blocks of 5 at a time, where possible. The splitting up into 5 requests is a good one. I have yet to have mirrorselect work in automatic mode for the past several versions. I'll be anxious to try it when it's ready. -Dan mirrorselect-0.7 has now been comitted to portage testing. this contains a block-select update to allow it to bypass routers which block over a certain number of simultaneous(sp?) lookups. (appears to not select anything if you run -a -s4) Please test away if this effects you. mirrorselect -a -s3 -b10 |