Package: apt-cacher
Version: 1.5.3
Severity: minor
Both the default apt-cacher.conf and the apt-cacher man page suggest you
can use either k or m as arguments to the limit option. The man page
goes as far as to suggest using man wget for the full syntax and claims
the default value is bytes/second.
In /usr/sbin/apt-cacher the config limit is handled by multiplying the
incoming value by 1024 and therefore limit is always in kB/sec. Any
suffix is irrelevant. I did notice the problem in practice so if the
following code does not seem to fully explain the problem there is
another cause lurking.
# for rate limit support
if($$cfg{limit}>0) {
$maxspeed = $$cfg{limit}*1024;
$getBufLen = $maxspeed/20; # 20 portions per second should be enough
}
The above code could be altered to allow further options or the
documentation could be updated to match the codes behaviour. As this
is a "compatible" version to a prior apt-cacher I don't know which is
preferable.
-- System Information:
Debian Release: 4.0
APT prefers unstable
APT policy: (500, 'unstable')
Architecture: amd64 (x86_64)
Shell: /bin/sh linked to /bin/bash
Kernel: Linux 2.6.19.2-slh64-smp-5
Locale: LANG=en_IE.UTF-8, LC_CTYPE=en_IE.UTF-8 (charmap=UTF-8)
Versions of packages apt-cacher depends on:
ii bzip2 1.0.3-6 high-quality block-sorting file co
ii libwww-perl 5.805-1 WWW client/server library for Perl
ii perl 5.8.8-7 Larry Wall's Practical Extraction
apt-cacher recommends no packages.
-- no debconf information
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
