From: Michel Lanners <mlan@cpu.lu>
To: jackal@aol.net
Cc: linuxppc-dev@lists.linuxppc.org
Subject: Re: no more processes crash
Date: Fri, 27 Aug 1999 07:48:26 +0200 (CEST) [thread overview]
Message-ID: <199908270548.HAA00486@piglet.cpu.lu> (raw)
In-Reply-To: <Pine.SGI.4.00.9908261904190.13884-100000@osiris.office.aol.com>
On 26 Aug, this message from brad allison echoed through cyberspace:
> This is a bad bug/crash. I suddenly am in a state of "No more processes".
>
> I'm not running much. Just about 10 aterms, netscape and aim.
>
[snip]
> Last thing I did was started a compile of kerberos. So the last command I
> ran was "make".
This might not be a Linux bug, but rather a Makefile bug in kerberos.
I've had this before, endless loops in a Makefile, so make restarts
itself all over again, until... you found the answer ;-).
Michel
-------------------------------------------------------------------------
Michel Lanners | " Read Philosophy. Study Art.
23, Rue Paul Henkes | Ask Questions. Make Mistakes.
L-1710 Luxembourg |
email mlan@cpu.lu |
http://www.cpu.lu/~mlan | Learn Always. "
[[ This message was sent via the linuxppc-dev mailing list. Replies are ]]
[[ not forced back to the list, so be sure to Cc linuxppc-dev if your ]]
[[ reply is of general interest. Please check http://lists.linuxppc.org/ ]]
[[ and http://www.linuxppc.org/ for useful information before posting. ]]
next parent reply other threads:[~1999-08-27 5:48 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <Pine.SGI.4.00.9908261904190.13884-100000@osiris.office.aol.com>
1999-08-27 5:48 ` Michel Lanners [this message]
[not found] <E11KJ0t-00076W-00@mail2.zrz.tu-berlin.de>
1999-08-27 14:33 ` no more processes crash brad allison
[not found] <Pine.SGI.4.00.9908271030280.15912-100000@osiris.office.aol.co m>
1999-09-12 20:15 ` brad allison
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=199908270548.HAA00486@piglet.cpu.lu \
--to=mlan@cpu.lu \
--cc=jackal@aol.net \
--cc=linuxppc-dev@lists.linuxppc.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).