Re: unkillable dpkg-query processes

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Wed, Oct 24, 2007 at 04:36:03PM -0700, David Miller wrote:
> > > 2) compiler used to build kernel and is it SMP?
> > 
> > gcc (GCC) 4.1.2 20061115 (prerelease) (Debian 4.1.1-21)
> > 
> > I've no idea if that compiler is SMP, if you want I'll ask someone else.
> 
> I was asking if the running kernel were SMP or not, I'll assume it is
> :-)

Oh, sorry, that sentence structure confused me (not a native speaker).

> > There doesn't appear to be a pattern, on this machine at least - I just let
> > the buildd run, building whatever comes up, and after a few hours it
> > inevitably runs into a wall.
> 
> If you try, within that troublesome build-root, a few times to try to
> fork off a couple hundred:
> 
> 	dpkg-query --something python-2.5
> 
> or whatever, can you get some of processes to wedge under that
> build root?

I did this in a chrooted bash:

for i in $(seq 0 100); do (dpkg-query -s python2.5-minimal > /dev/null &); done

And now the machine went catatonic. :(

Thankfully the console is still vaguely operational - I can enter my
username to log in, but I can't get the Password prompt to appear.
Magic SysRq still works - if you need any output from it, tell me.

-- 
     2. That which causes joy or happiness.
-
To unsubscribe from this list: send the line "unsubscribe sparclinux" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html

[Index of Archives]     [Kernel Development]     [DCCP]     [Linux ARM Development]     [Linux]     [Photo]     [Yosemite Help]     [Linux ARM Kernel]     [Linux SCSI]     [Linux x86_64]     [Linux Hams]

  Powered by Linux