tags 291152 +pending thanks On Tue, Jan 18, 2005 at 07:21:15PM -0600, Micah Anderson wrote: > Package: debpool > Version: 0.1.9 > Severity: important > > Invoking debpool with --daemon causes it to be power hungry, eating as > much as it can get its dirty little hands on. As you can see from the > following, debpool is running at 99.8% CPU utilization, and that is > while it is not doing ANYTHING AT ALL, except chewing CPU. > > 5908 debpool 25 0 7232 5756 2792 R 99.8 0.6 10:44.31 debpool > > This makes debpool pretty much useless in daemon mode, and forces me > to run it in the far inferior crontab mode. > > Micah
Problem found. The documentation discusses the default sleep being 300
seconds, or 5 minutes - which it should be. However, the final fallback
config file (which would often be used in this case) somehow had it set to
0, instead of 300, thus resulting in a tight spinloop in Monitor_Incoming.
Fixed in SVN, will be fixed in 0.1.10; workaround in the meanwhile is, of
course, to specify 'sleep' in at least one of /etc/debpool/Config.pm or
~/.debpool/Config.pm (or, as you state, use a cron job to fire it).
Some useful logging added to the Monitor_Incoming routine to make it more
obvious when something is awry there.
--
Joel Aelwyn <[EMAIL PROTECTED]> ,''`.
: :' :
`. `'
`-
signature.asc
Description: Digital signature
