On Fri, Jan 25, 2008 at 01:29:47PM +0200, Dmitry Nezhevenko wrote:
> Package: apt-cacher
> Version: 1.6.1
> Severity: normal
>
> currently apt-cacher just ignores it. So it uses all available bandwidth.
> version 1.5.5 has no such bug
Thanks. 1.6 uses libcurl which has native bandwidth limiting.
What is your limit setting?
Could you apply this patch to /usr/share/apt-cacher/apt-cacher and post
the relevant bit of /var/log/apt-cacher/error.log
Mark
diff --git a/apt-cacher b/apt-cacher
index 7560a02..2caea2a 100755
--- a/apt-cacher2
+++ b/apt-cacher2
@@ -1167,7 +1167,10 @@ sub body_callback {
/^(\d+)m$/ && do { $maxspeed = $1 * 1048576; last; };
warn "Unreconised limit: $_. Ignoring.";
}
- $curl->setopt(CURLOPT_MAX_RECV_SPEED_LARGE, $maxspeed) if $maxspeed;
+ if ($maxspeed) {
+ info_message("Setting bandwidth limit to $maxspeed");
+ $curl->setopt(CURLOPT_MAX_RECV_SPEED_LARGE, $maxspeed);
+ }
return \$curl;
}
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]