Skip site navigation (1)Skip section navigation (2)
Date:      Tue, 11 Jun 1996 09:23:22 +0000
From:      steve farrell <spfarrel@midway.uchicago.edu>
To:        questions@freebsd.org
Subject:   cannot fork with freebsd-stable
Message-ID:  <31BD3AEC.41C67EA6@midway.uchicago.edu>

next in thread | raw e-mail | index | archive | help
i recently installed freebsd-2.1R, and since supped -stable, compiled a
new kernel and set of libraries.  since then i've been having the
following problem:  i get an error that i cannot fork a new process
(actually, as root i usually can, but not always -- i guess this is
supposed to protect against denial of service attacks...anyway....).  i
thought at first that this was due to the fact that the libraries had
changed on a live system, so i baked a new kernel (i set the max users
up to 40 in case the process table was running out?) and rebooted.  24
hours later i'm having the same problem!  help please, i don't want ot
have to reboot every day! 

verbatim:

zsh: fork failed: resource temporarily unavailable [92]

(though, the number 92, i'm quite sure, is different from yesterday.  i
think it was 250 or something yesterday...)

(also, there are nowhere near 20 + 16 * 40 processes running right now
-- actually there are 62 -- speaking of which, that seems to be my new
hard limit =( ....until i reboot, at least.)


system:

486-80Mhz, 48MB RAM 



machine         "i386"
cpu             "I486_CPU"
ident           "EUTHYPHRO"
maxusers        40

options         INET                    #InterNETworking
options         FFS                     #Berkeley Fast Filesystem
options         NFS                     #Network Filesystem
options         MSDOSFS                 #MSDOS Filesystem
options         PROCFS                  #Process filesystem
options         "COMPAT_43"             #Compatible with BSD 4.3
options         "SCSI_DELAY=5"          #Be pessimistic about Joe 
options         BOUNCE_BUFFERS          #include support for DMA b
options         UCONSOLE                #Allow users to grab the c

options         SYSVSHM
options         SYSVSEM
options         SYSVMSG

config          kernel  root on  sd0

controller      isa0

controller      fdc0    at isa? port "IO_FD1" bio irq 6 drq 2 vect
disk            fd0     at fdc0 drive 0

controller      wdc0    at isa? port "IO_WD1" bio irq 14 vector wd
disk            wd0     at wdc0 drive 0

options         ATAPI   #Enable ATAPI support for IDE bus
device          wcc1    #IDE CD-ROM

controller      aha0    at isa? port "IO_AHA0" bio irq ? drq 5 vec

controller      scbus0

device          sd0


# syscons is the default console driver, resembling an SCO console
device          sc0     at isa? port "IO_KBD" tty irq 1 vector sci
# Enable this and PCVT_FREEBSD for pcvt vt220 compatible console d
#device         vt0     at isa? port "IO_KBD" tty irq 1 vector pcr
#options                "PCVT_FREEBSD=210"      # pcvt running on 
#options                XSERVER                 # include code for

device          npx0    at isa? port "IO_NPX" irq 13 vector npxint

device          sio0    at isa? port "IO_COM1" tty irq 4 vector si
device          sio1    at isa? port "IO_COM2" tty irq 3 vector si
device          lpt0    at isa? port? tty irq 7 vector lptintr


# Order is important here due to intrusive probes, do *not* alphab
# this list of network interfaces until the probes have been fixed
# Right now it appears that the ie0 must be probed before ep0. See
# revision 1.20 of this file.
device ed1 at isa? port 0x300 net irq  5 iomem 0xd8000 vector edin

pseudo-device   loop
pseudo-device   ether
pseudo-device   log
pseudo-device   sl      1
# ijppp uses tun instead of ppp device
pseudo-device   tun     1
pseudo-device   pty     16
pseudo-device   gzip            # Exec gzipped a.out's


thanks!

--steve farrell (who otherwise thinks freebsd is pretty damn nice...)



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?31BD3AEC.41C67EA6>