On 8/23/06, Dylan Thurston <[EMAIL PROTECTED]> wrote:
On Thu, Aug 24, 2006 at 10:31:23AM +1000, Brendan O'Dea wrote:
> On Tue, Aug 22, 2006 at 10:03:33AM -0700, Debian Bug Tracking System wrote:
> >> reassign 351963 debsums
> >Bug#351963: reportbug: "Checking package integrity" seems to loop on mzscheme
> >Bug reassigned from package `reportbug' to `debsums'.
>
> The original report stated that reportbug, not debsums was pegging CPU
> at 100%. Dylan, can you confirm? What happens when you run
> "debsums -s mzscheme" at the command line? Try again without -s if it hangs.
The bug is unfortunately not reproducible now; it probably occurred
because drscheme was in a half-installed state. I believe it was
'reportbug' and not 'debsums' that was taking all the CPU, but I can not
be certain. 'debsums -s mzscheme' now takes a few seconds and uses
mostly disk access, not CPU.
The bug report states that mzscheme depends on drscheme, but in fact the
dependency is the other way. I'm not sure what the situation was.
Sorry I can't be more help now.
I'm at a loss to figure how reportbug would be pegging the CPU; it's
using blocking IO to read the pipe, so read(2) would be sleeping the
process while debsums runs.
Not to say it's impossible... just unlikely. And apparently unreproducible...
Chris
--
Chris Lawrence - http://blog.lordsutch.com/
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
