From owner-freebsd-current Wed Apr 12 07:11:27 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id HAA13997 for current-outgoing; Wed, 12 Apr 1995 07:11:27 -0700 Received: from trout.sri.MT.net (trout.sri.MT.net [204.182.243.12]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id HAA13986 for ; Wed, 12 Apr 1995 07:11:16 -0700 Received: (from nate@localhost) by trout.sri.MT.net (8.6.11/8.6.10) id IAA13455; Wed, 12 Apr 1995 08:10:24 -0600 Date: Wed, 12 Apr 1995 08:10:24 -0600 Message-Id: <199504121410.IAA13455@trout.sri.MT.net> To: Christoph Kukulies Cc: freebsd-current@freefall.cdrom.com (user alias) Subject: Re: too many open files In-Reply-To: <199504120758.JAA02330@gilberto.physik.rwth-aachen.de> References: <199504111738.TAA19045@gilberto.physik.rwth-aachen.de> <199504120758.JAA02330@gilberto.physik.rwth-aachen.de> Reply-To: nate@sneezy.sri.com (Nate Williams) From: nate@sneezy.sri.com (Nate Williams) Sender: current-owner@FreeBSD.org Precedence: bulk Christoph Kukulies writes: > Answering to myself: > > Forgot to mention that also sup is running (client) on this machine. > Does or did sup have a resource leak problem in that it opens too many files > and doesn't close them ? (although this shouldn't result in a kernel > message). Nope. Sup opens/closes one file at a time aside from the sup file and the sockets. Nate