From owner-freebsd-questions@FreeBSD.ORG Tue Feb 8 21:23:05 2005 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 6699416A4CE for ; Tue, 8 Feb 2005 21:23:05 +0000 (GMT) Received: from mail23.sea5.speakeasy.net (mail23.sea5.speakeasy.net [69.17.117.25]) by mx1.FreeBSD.org (Postfix) with ESMTP id 3398543D46 for ; Tue, 8 Feb 2005 21:23:05 +0000 (GMT) (envelope-from freebsd-questions-local@be-well.ilk.org) Received: (qmail 14529 invoked from network); 8 Feb 2005 21:23:05 -0000 Received: from dsl092-078-145.bos1.dsl.speakeasy.net (HELO be-well.ilk.org) ([66.92.78.145]) (envelope-sender ) by mail23.sea5.speakeasy.net (qmail-ldap-1.03) with SMTP for ; 8 Feb 2005 21:23:04 -0000 Received: by be-well.ilk.org (Postfix, from userid 1147) id E7A5F44; Tue, 8 Feb 2005 16:23:03 -0500 (EST) Sender: lowell@be-well.ilk.org To: dreyes@eaznet.com References: <20050208192555.00E50106D73@mail.eaznet.com> From: Lowell Gilbert Date: 08 Feb 2005 16:23:03 -0500 In-Reply-To: <20050208192555.00E50106D73@mail.eaznet.com> Message-ID: <44k6piyceg.fsf@be-well.ilk.org> Lines: 14 User-Agent: Gnus/5.09 (Gnus v5.9.0) Emacs/21.3 MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: quoted-printable cc: freebsd-questions@freebsd.org Subject: Re: help with foxpro and FreeBSD 4.5 X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: freebsd-questions@freebsd.org List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 08 Feb 2005 21:23:05 -0000 "Dante Reyes" writes: > I am currently trying to install FoxPro 2.6 for unix onto FreeBSD 4.5.=A0 > However, any time I try to run FoxPro, I get the message "Too many files > open."=A0 After doing some research, it does not appear a file handling > problem. I'll ignore that last sentence, as I can't parse it in a way that provides any information that could solve the problem. You could be running into user limits or system limits. The user limits are visible through the limits(1) command, and the system limits are visible through sysctl(8) (kern.maxfiles, kern.maxfilesperproc, kern.openfiles).