I had a cauldron HTTP install going on an internal machine, and bounced my DNS server. I immediately got an error for the next package to be installed, which tells me that the installer requires DNS resolution for each package request, even if it's using the same server repeatedly. It seems like making a DNS call once at the start of the install (or whenever a new server comes into play), and then using the IP address directly for subsequent requests would save quite a bit of DNS overhead and network chatter.
We fork curl to fetch packages which thus lost its cached value on exiting after downloading packages for a transaction so it's not just a matter of caching return of resolver. Including a DNS cache such as nscd looks a bit overkill to me
Priority: Normal => LowCC: (none) => thierry.vignaud
I wouldn't go as far as to recommend adding nscd, since we're only using one server at a time. What's wrong with doing a gethostbyname() whenever we switch to a server, and then just passing the IP address to curl ?
Fell free to suggest & test a patch for urpm/download.pm. (See /usr/lib/perl5/vendor_perl/5.14.2/urpm/download.pm) Should be done in sync_rel()
Source RPM: (none) => urpmi
OK, as its an enhancement, leave it to me to play with. Thanks for the pointer. I'll brush up on my perl :-)
Hi, This bug was filed against cauldron, but we do not have cauldron at the moment. Please report whether this bug is still valid for Mageia 2. Thanks :) Cheers, marja
Keywords: (none) => NEEDINFO
Keywords: NEEDINFO => (none)
This is one of 8 hyper-stale bugs and enhancement requests (other than package requests) that are now being closed as old. Each of them * is still assigned to BugSquad instead of to a maintainer * did not see any action since June 2012 If this one is still valid, then please reopen it. In that case: don't be shocked that I closed it: There is more chance it'll get fixed after it's wrongly closed and then reopened again (because of the mails Bugzilla sends to many packagers etc. when there is some action in a bug), than when nothing happens in this report for some more years :-)
Status: NEW => RESOLVEDResolution: (none) => OLD