Odd Behaviour with netselect-apt
Introduction
netselect-apt∞ is a package that will find the Debian mirror which presently offers the fastest response time to your system; it does this by pulling down a full list of mirrors and then using
netselect to determine relative download speeds. It's a logical extension of
netselect∞ to relieve the administrator from having to manually select mirrors to test;
all of them get tested.
The Problem
On Sunday 15 January 2005, I used
netselect-apt to find the fastest sites via the following procedure:
:code:(bash)
netselect-apt -s -n -o /tmp/sources.experimental experimental
netselect-apt -s -n -o /tmp/sources.unstable unstable
netselect-apt -s -n -o /tmp/sources.testing testing
netselect-apt -s -n -o /tmp/sources.stable stable
grep -hv ^# /tmp/sources.*
/etc/apt/sources.list
vi /etc/apt/sources.list
:code:
thereupon moving the relevant lines tacked onto the end of the file into the appropriate places in the file.
Running
apt-get update against the newly modified
sources.list file gave errors
:code:
> Reading Package Lists...Error!
> E: Dynamic MMap ran out of room
> E: Dynamic MMap ran out of room
> E: Problem with
MergeList?
> E: The package lists or status file could not be parsed or opened.
:code:
Resetting the contents of the
sources.list file back to the original contents (using the
ftp.de.debian.org mirror, which is very slow from here) did not exhibit the problem, nor did using a (better but not optimal)
ftp2?.jp.debian.org mirror.
Anybody with any ideas, please feel free to edit this or email me at jdickey at seven-sigma dot com. Thanks
