Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP Path: utzoo!mnetor!seismo!ut-sally!ut-ngp!melpad!bigtex!james From: james@bigtex.uucp (James Van Artsdalen) Newsgroups: comp.unix.questions Subject: Re: ulimit considered braindamaged ? Message-ID: <210@bigtex.uucp> Date: Mon, 5-Jan-87 11:17:52 EST Article-I.D.: bigtex.210 Posted: Mon Jan 5 11:17:52 1987 Date-Received: Mon, 5-Jan-87 23:11:38 EST References: <790@maynard.BSW.COM> <166@herman.UUCP> Sender: news@bigtex.uucp Reply-To: james@bigtex.UUCP (James Van Artsdalen) Organization: F.B.N. Software, Austin TX Lines: 15 Keywords: ulimit SysV irksome IN article <166@herman.UUCP>, det@herman.UUCP (Derek Terveer) wrote: >You can change the system-wide default value for ulimit by, assuming of course >that you have a source code license, changing a constant in the unix source and >simply recompiling. I believe the constant is called MAXWRITE or something >like that. If you really want to know the details, get back to me. It isn't even necessary to have a source code license. For the record, all that appears necessary is to up the ulimit in rc2 so that cron and processes cron runs hvae a higher ulimit, and to modify one of the public domain login programs to up the ulimit. The cron ulimit should be as high or higher than the ulimit for any user from login; if not, there is a problem trying to run "at" or "batch" jobs (or you could modify /usr/lib/cron/.proto I suppose). -- James R. Van Artsdalen ...!ut-sally!utastro!bigtex!james "Live Free or Die" Voice: (512)-323-2675 Modem: (512)-323-2773 5300B McCandless, Austin TX 78756