Excerpts from Jonathan Nieder's message of sáb ago 20 23:47:04 -0400 2011:
> tags 545701 + moreinfo
> quit
>
> Jonathan Nieder wrote:
> > Alvaro Herrera wrote on 2009-09-08:
>
> >> I started an aptitude safe-upgrade and left the computer for half an
> >> hour. Upon return I find that there's a suspicious process eating 100%
> >> of a CPU for a long time.
> [...]
> >> /usr/bin/perl-w/usr/share/debconf/frontend/var/lib/dpkg/info/dash.postinstabort-upgrade0.5.5.1-2.3
> [...]
> >> ioctl(0, SNDCTL_TMR_TIMEBASE or TCGETS, {B0 -opost -isig icanon -echo
> >> ...}) = 0
> >> <repeats ad nauseam>
> >
> > (isatty, I think.)
>
> If I had to guess, this loop is somewhere in the guts of debconf
> machinery. So I fear it was probably silently fixed.
Yeah, perhaps.
> But still:
>
> - do you remember anything more about what was happening when this
> occured (for example, did you interrupt any previous upgrade, and
> was there a terminal available)?
No previous interrupted upgrades.
> - did it ever happen again?
Nope. I happened to notice now that I reported that I was using
aptitude to upgrade. I no longer do that; I always use apt-get now.
Not sure if that means anything.
> - any other clues or symptoms?
I don't really remember anything else.
> Sorry we didn't get to this in time.
Yeah ... I guess this can safely be closed.
--
Álvaro Herrera <alvhe...@alvh.no-ip.org>
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
