On Thu, 2009-07-23 at 22:16 +0100, Mark Hindley wrote: > On Thu, Jul 23, 2009 at 02:10:35PM -0700, Ross Boylan wrote: > > No luck. Same or worse behavior as before. > > > > During aptitude update > > apt-cacher shows as using most CPU. > > Has this always been the case with 1.6.8? Yes. > Did something else change? The only thing that may have changed after application of the patch is that the throughput went down. But I'm not sure how good it was before. > > > Throughput well below my link speed (this is the part that might be > > worse than before). > > > > During aptitude upgrade, while pulling in debs > > apt-cacher shows as using most cpu. The offending thread says still > > lists apt-cacher as the command line, but has [libcurl] afterwards. > > Is that thread idle? No; it's the one using all the CPU. > Does it not exit after about 2 minutes? I haven't timed it exactly, but I think it disappears after a decent interval.
Ross > I expect it > to be there, but idle and then exit after being unused for 120 seconds > > > > > Ross > > > > P.S. Your last message appeared to cc submit but not the bug itself. > > Yes, I noticed that and sent a copy to debian bugs as well > > Mark > -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected]
