From owner-freebsd-hackers Wed Feb 12 16:35:07 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id QAA06046 for hackers-outgoing; Wed, 12 Feb 1997 16:35:07 -0800 (PST) Received: from oneway.com (oneway.com [198.80.68.27]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id QAA06010; Wed, 12 Feb 1997 16:34:48 -0800 (PST) Received: from localhost (jaykuri@localhost) by oneway.com (8.8.3/8.8.3) with SMTP id SAA23679; Wed, 12 Feb 1997 18:29:59 -0600 (CST) Date: Wed, 12 Feb 1997 18:29:59 -0600 (CST) From: Jay Kuri Reply-To: Jay Kuri To: hackers@freebsd.org, questions@freebsd.org cc: Wes Peters Subject: Max open files per process, changing param.c Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Hello, I'm working on some programs that require very large numbers of files open per process. 200-500 easily. I've done some research, and came to /usr/src/sys/conf/param.c... I notice that the system-wide-limit for open files is the same as the per-process-limit for open files. My main question is this: What, if any, ramifications will changing 'maxfiles' in param.c to increase max open files system-wide? If 'maxfilesperproc' is different from 'maxfiles' will that cause any problems? Additionally, Will I run into other problems with regard to high file descriptor numbers? I know that on Solaris (2.5 anyway) even though you can kick the max-open-files per process up to 2048, the FILE structure limits the file descriptor number to 1 byte, to 256 total. Will I run into similar problems with FreeBSD? Any Help would be appreciated, Jay --- Everyone can be taught to sculpt: Michelangelo would have had to be taught how not to. So it is with the great programmers.