On Mon, Jan 28, 2008 at 01:31:04PM +0000, Dmitry Nezhevenko wrote: > On Mon, Jan 28, 2008 at 01:13:40PM +0000, Mark Hindley wrote: > > 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 > > > > Done. I have just set limit: limit=10k. However apt-get shows: 71,2kB/s.
That isn't necessarily the same thing. The limit option (currently) limits the download speed to apt-cacher from upstream. The speed between a client and the apt-cacher server is not controlled. Do you think it should? Is that what you were expecting? > Here is a line from error.log: > info [13057]: Setting bandwidth limit to 10240 Seems OK. Mark -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
