From owner-freebsd-questions Tue Sep 1 00:35:52 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id AAA05515 for freebsd-questions-outgoing; Tue, 1 Sep 1998 00:35:52 -0700 (PDT) (envelope-from owner-freebsd-questions@FreeBSD.ORG) Received: from hotmail.com (f229.hotmail.com [207.82.251.120]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id AAA05510 for ; Tue, 1 Sep 1998 00:35:50 -0700 (PDT) (envelope-from tkined@hotmail.com) Received: (qmail 14810 invoked by uid 0); 1 Sep 1998 07:34:51 -0000 Message-ID: <19980901073451.14809.qmail@hotmail.com> Received: from 202.135.160.10 by www.hotmail.com with HTTP; Tue, 01 Sep 1998 00:34:42 PDT X-Originating-IP: [202.135.160.10] From: "HW Wong" To: freebsd-questions@FreeBSD.ORG, lists@alpha.nl Subject: Process table full?? Content-Type: text/plain Date: Tue, 01 Sep 1998 00:34:42 PDT Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi all: I am running a script to simulate login to webserver using a software call webcopy (written in Perl). The script will call the webcopy and put it to background. And this will continue for 1000 users. I found out that, it will stop at around 280 users. Then the error message, cannot fork will appear. As a workaround, I tried to run it over 200 users and put a wait command after 200, then run 200 again , wait, run 200 again. I found out that, there after running the first 200 users, it will pending for nothing. When I do a ps, I found out there are always a few processes never finished. I am not sure whether this is related to Perl and memory leak problem. But somehow it is coincidence with the problem describe below. Any clues?? HW > >Yesterday and the day before I've been reporting hanging Perl-processes >spawned by the Apache webserver. these processes fetch some data from an >NFS-partition on a different system. I'm getting the idea that this NFS is >causing the problems. Some commands freeze up (say a tail -1500 is done over >NFS on a file containing 7500 lines) and I think this is the cause of our >'memory leaks'. These processes stay in memory and can't be killed. Does >anyone have any suggestions on how I could prevent this from happening? > >Arjan > > >To Unsubscribe: send mail to majordomo@FreeBSD.org >with "unsubscribe freebsd-questions" in the body of the message > ______________________________________________________ Get Your Private, Free Email at http://www.hotmail.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message