From owner-freebsd-questions Sat Nov 4 06:55:57 1995 Return-Path: owner-questions Received: (from root@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id GAA24031 for questions-outgoing; Sat, 4 Nov 1995 06:55:57 -0800 Received: from metronet.com (pgilley@fohnix.metronet.com [192.245.137.2]) by freefall.freebsd.org (8.6.12/8.6.6) with SMTP id GAA24022 for ; Sat, 4 Nov 1995 06:55:51 -0800 Received: by metronet.com id AA00037 (5.67a/IDA1.5hp for questions@freebsd.org); Sat, 4 Nov 1995 08:55:34 -0600 Date: Sat, 4 Nov 1995 08:55:33 -0600 (CST) From: Phil Gilley To: questions@freebsd.org Subject: portmap problem Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-questions@freebsd.org Precedence: bulk After 8 days of uptime, one of my FreeBSD 2.0.5-RELEASE machines has started complaining about: Nov 3 20:00:42 sunra portmap[68]: CALLIT (prog 100004): fork: Resource temporarily unavailable Nov 3 20:01:36 sunra last message repeated 7 times Nov 3 20:02:30 sunra last message repeated 14 times Nov 3 20:11:52 sunra last message repeated 63 times Nov 3 20:23:24 sunra last message repeated 59 times Nov 3 20:33:20 sunra last message repeated 91 times ...and so on. And depending on when I do a ps, I might see: USER PID %CPU %MEM VSZ RSS TT STAT STARTED TIME COMMAND daemon 68 2.2 1.7 176 244 ?? SNs 27Oct95 39:57.00 portmap daemon 3221 1.0 1.5 200 216 ?? SN 8:55AM 0:00.01 portmap daemon 3212 0.5 1.5 200 216 ?? SN 8:55AM 0:00.02 portmap daemon 3213 0.5 1.5 200 216 ?? SN 8:55AM 0:00.02 portmap daemon 3214 0.5 1.5 200 216 ?? SN 8:55AM 0:00.02 portmap daemon 3215 0.5 1.5 200 216 ?? SN 8:55AM 0:00.01 portmap daemon 3216 0.5 1.5 200 216 ?? SN 8:55AM 0:00.02 portmap daemon 3217 1.0 1.5 200 216 ?? SN 8:55AM 0:00.01 portmap daemon 3218 0.5 1.5 200 216 ?? SN 8:55AM 0:00.01 portmap daemon 3219 0.5 1.5 200 216 ?? SN 8:55AM 0:00.01 portmap daemon 3220 1.5 1.5 200 216 ?? SN 8:55AM 0:00.02 portmap ...and so on up to 20 or so processes. Other times when I do a ps, I just see one portmap process. Does anyone know what the problem might be? Phil Gilley pgilley@metronet.com