Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP Path: utzoo!mnetor!seismo!mcvax!diku!olamb!kimcm From: kimcm@olamb.UUCP (Kim Chr. Madsen) Newsgroups: comp.unix.wizards Subject: Re: Determining the max number of open files on System V Message-ID: <292@olamb.UUCP> Date: Wed, 3-Jun-87 07:31:46 EDT Article-I.D.: olamb.292 Posted: Wed Jun 3 07:31:46 1987 Date-Received: Wed, 10-Jun-87 02:02:25 EDT References: <3635@spool.WISC.EDU> Organization: AmbraSoft A/S (Denmark) Lines: 27 Keywords: NOFILES, S5R3 In article <3635@spool.WISC.EDU>, dave@romano.WISC.EDU (Dave Cohrs) writes: > Originally I thought, "Oh, that's, easy, just include > and close 0 through NOFILE". Well, I looked at and > it said, > > "The following define is here for temporary compatibility > and should be removed in the next release. It gives a > value for the maximum number of open files per process. > However, this value is no longer a constant." > > So, where do I get the real value? What is "v.v_nofiles" and how do > I get at it's value? If you just want to know the actual number run the command "/etc/sysdef", which gives you the current settings of the turnable kernel parameters and other system information. Or look into the /etc/master.d/kernel file. But if you want to inspect the max. number of open files at runtime, you must use the value stored in the kernel. > Please, don't tell me I have to muck around in kernel memory! Don't panic use the nlist(3C) call with the v structure (defined in ) the value of v.v_nofiles contains the actual value. Regards Kim Chr. Madsen