From owner-freebsd-questions Wed Aug 26 01:50:42 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id BAA26509 for freebsd-questions-outgoing; Wed, 26 Aug 1998 01:50:42 -0700 (PDT) (envelope-from owner-freebsd-questions@FreeBSD.ORG) Received: from smtp3.xs4all.nl (smtp3.xs4all.nl [194.109.6.53]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id BAA26504 for ; Wed, 26 Aug 1998 01:50:39 -0700 (PDT) (envelope-from lists@alpha.nl) Received: from lisboa ([194.109.98.152]) by smtp3.xs4all.nl (8.8.8/8.8.8) with SMTP id KAA15727; Wed, 26 Aug 1998 10:49:49 +0200 (CEST) Message-ID: <00d801bdd0cf$43cbf690$98626dc2@lisboa.nedstat.nl> From: "Arjan" To: Subject: How stable is NFS in FreeBSD? Date: Wed, 26 Aug 1998 10:55:24 +0200 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 4.72.3110.5 X-MimeOLE: Produced By Microsoft MimeOLE V4.72.3110.3 Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG 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