Return to BSD News archive
Xref: sserve comp.os.386bsd.bugs:1287 comp.os.386bsd.questions:4651 comp.os.386bsd.misc:776
Path: sserve!newshost.anu.edu.au!cairo!titus
From: titus@cairo.anu.edu.au (titus chiu)
Newsgroups: comp.os.386bsd.bugs,comp.os.386bsd.questions,comp.os.386bsd.misc
Subject: that annoying bug..
Date: 27 Aug 1993 22:27:40 GMT
Organization: Coombs Computing Unit, Australian National University, Canberra.
Lines: 31
Distribution: world
Message-ID: <25m1os$9q8@manuel.anu.edu.au>
NNTP-Posting-Host: 150.203.76.16
X-Disclaimer: This message was written by a user on Coombs at ANU. The
opinions expressed are those of the user and not necessarily
those of the Australian National University.
hi there,
I posted about this a week or so ago and got 1 reply saying
"oh its in all netbsd systems, i think we have it fixed", but didnt
say what bug it was OR where it is fixed. Now the bug is that every
so often (very often ;P) a netbsd system would stop forking new
processes. Old processes seems to keep running for a while before
they die. The machine doesnt hang or reboot, but just sits there. For
example if i telnet to it now i get a connect (since inetd is still
running and listening to the port) but it is unable to run telnetd
and it simply sits there doing nothing. We have installed netbsd 0.9
thinking it might be fixed but to no avail. Does anyone know what the
actual bug is and/or if there is a fix for it? I dont think it is
because it is running out of memory beacuse we have plenty of swap.
The machine only seem to do this with a bit of load (tho not always)
could it be that the process table is too small and is getting filled
up? Our setup is :
80486DX/50
8 megs of system memory
24 megs of swap
170 meg conners HD (cp30174e)
ide controller and FDD etc
regards
titus chiu
--
titus chiu -- email: ---------------------
-- titus@cairo.anu.edu.au -----
dont drink and drive home -- titus@raid.ctpm.uq.oz.au ---
get stoned and fly home. -------------------------------