Package: apt Version: 0.5.28.1 Hello,
since I'm currently still using a 56K connection, I wanted to employ user-space bandwidth shaping to have lower download rates for certain processes. I discovered that this works nicely using wget, but using apt, it also works (nicely shaped at 2KB/s), yet both its ftp and http methods use as much CPU power as they can get. This is with trickle version 1.07-3, in a setup that's NOT using trickled (the daemon). A sample cmdline used is trickle -d 2 apt-get install evolution Since both wget (1.9.1-8) and curl (7.13.1-2) manage to work nicely without a CPU busy loop (wget -c ftp://ftp.de.debian.org/pub/debian/ls-lR), I'd assume this to be a fatal issue in apt's http/ftp methods' socket event loop or so. Together with bugs #146877, #156578, #179384, #240417 and #270869 which all would like to see bandwidth limiting within apt itself, this is cause for concern since not even with non-native solutions limiting works properly (apart from kernel-space shaping, which does work but cannot easily employ per-process settings). These are package versions on a testing test setup, but the same issue also happens equally with newer versions of all these packages in my Debian unstable machine (which I currently cannot access). Thank you for an outstanding package management mechanism! Andreas Mohr -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]