On Sun, 08 Sep 2002 12:19:21 PDT, Alex Withers writes:
>On Sun, 8 Sep 2002, Nicos Gollan wrote:
>As it turns out that was it, in a way. I had a line in my .bashrc that
>went like so: PAGER=`which less`. For some reason this would cause a
>momentary explosion in the number of "which" processes.
On Sunday 08 September 2002 19:24, Elizabeth Barham wrote:
> Nicos Gollan <[EMAIL PROTECTED]> writes:
> > We had this on the list some days ago. Run ps ax and see if you've
> > got a huge quantity of (defunct) processes.
>
> I must have missed that thread; what ever became of it?
The last thread
On Sun, Sep 08, 2002 at 12:19:21PM -0700, Alex Withers wrote:
> On Sun, 8 Sep 2002, Nicos Gollan wrote:
> > We had this on the list some days ago. Run ps ax and see if you've got a
> > huge quantity of (defunct) processes.
>
> As it turns out that was it, in a way. I had a line in my .bashrc tha
On Sun, 8 Sep 2002, Nicos Gollan wrote:
> On Sunday 08 September 2002 17:33, Alex Withers wrote:
> > Hello, I've recently installed Debian 3.0 on a home machine. After
> > logging into the machine through xdm I open an xterm with no trouble
> > but when I try to spawn another xterm it hangs for
Nicos Gollan <[EMAIL PROTECTED]> writes:
> We had this on the list some days ago. Run ps ax and see if you've
> got a huge quantity of (defunct) processes.
I must have missed that thread; what ever became of it? I've recently
noticed that my server has had a large number of defunct processes on
On Sunday 08 September 2002 17:33, Alex Withers wrote:
> Hello, I've recently installed Debian 3.0 on a home machine. After
> logging into the machine through xdm I open an xterm with no trouble
> but when I try to spawn another xterm it hangs for a few seconds
> before spitting out the message:
Alex Withers said:
>
> Hello, I've recently installed Debian 3.0 on a home machine. After
> logging into the machine through xdm I open an xterm with no trouble but
> when I try to spawn another xterm it hangs for a few seconds before
> spitting out the message: "bash: fork: Resource temporarily
antom processes when the user had already logged
out)
Rob...
- Original Message -
From: "Andrei Ivanov" <[EMAIL PROTECTED]>
To: "Imre Vida" <[EMAIL PROTECTED]>
Cc:
Sent: Saturday, June 09, 2001 5:44 AM
Subject: Re: bash: fork: Resource temporarily unavaila
As a different post has suggested, it probably is a mixture of process and
file table problem. The best solution would have been to reboot the
system, and then pay close attention to it over the next few days to see
how it goes. Also, as some processes die and before new ones spawn, you
may be able
on Fri, Jun 08, 2001 at 11:06:07PM +0200, Imre Vida ([EMAIL PROTECTED]) wrote:
>
> one more bit of info:
> I can ftp to the machine.
> This works absolutely fine.
> Funny.
Resources come in several flavors. I'd suspect process table or open
files. Note that some daemons run without spawning new
one more bit of info:
I can ftp to the machine.
This works absolutely fine.
Funny.
imre
Andrei,
thanks for your response
> I've seen this before, and it has got something to do with too many
> processes running on the system, eating up the file descriptor table. We
> had a system in the office that had 50-some instances of a process
> running, and were getting this message (I believ
> Hi,
>
> i seem to have a problem with my Debian box.
>
> When i try to login to it using ssh it accepts
> the login but then instead of the bash prompt
> i get the following erromsg:
>
> bash: fork: Resource temporarily unavailable
>
> This has never happened before and i didn't
> anythi
13 matches
Mail list logo
