From owner-freebsd-questions Tue Apr 22 17:39:53 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id RAA20749 for questions-outgoing; Tue, 22 Apr 1997 17:39:53 -0700 (PDT) Received: from gdi.uoregon.edu (gdi.uoregon.edu [128.223.170.30]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id RAA20741 for ; Tue, 22 Apr 1997 17:39:51 -0700 (PDT) Received: from localhost (dwhite@localhost) by gdi.uoregon.edu (8.8.5/8.6.12) with SMTP id RAA25174; Tue, 22 Apr 1997 17:39:49 -0700 (PDT) Date: Tue, 22 Apr 1997 17:39:49 -0700 (PDT) From: Doug White X-Sender: dwhite@localhost Reply-To: Doug White To: Robert Watson cc: questions@freebsd.org Subject: Re: File Table full In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-questions@freebsd.org X-Loop: FreeBSD.org Precedence: bulk On Tue, 22 Apr 1997, Robert Watson wrote: > > > Apr 21 12:08:56 fledge syslogd: /dev/console: Too many open files in > > > system: Too > > > many open files in system > > > > Not really. You want to probably tweak CHILD_MAX and OPEN_MAX. > > I was unsure if this was a user hitting a by-uid limit on files, or if the > actual system table for all file descriptors was being hit? Is there any > way to find out a) if it was a specific user or the system, and b) if it > was a specific user, who it was so I could find out what program ran into > the problem? I wouldn't know. If the machine's been up for a while, it may be due for a reboot. fstat may help you find what program is holding a lot of files open. Doug White | University of Oregon Internet: dwhite@resnet.uoregon.edu | Residence Networking Assistant http://gladstone.uoregon.edu/~dwhite | Computer Science Major