Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!uflorida!haven!uvaarpa!virginia!scl
From: scl@virginia.acc.virginia.edu (Steve Losen)
Newsgroups: comp.bugs.sys5
Subject: Re: ulimit -- You don't need sources! (kind of long)
Keywords: ulimit
Message-ID: <2408@virginia.acc.virginia.edu>
Date: 5 May 89 13:42:07 GMT
References: <836@twwells.uucp> <4428@ihuxz.ATT.COM> <545@aurora.AthabascaU.CA> <8305@chinet.chi.il.us> <5627@xyzzy.UUCP> <562@aurora.AthabascaU.CA>
Reply-To: scl@virginia.acc.Virginia.EDU (Steve Losen)
Organization: University of Va., Charlottesville, VA
Lines: 15

In article <562@aurora.AthabascaU.CA> lyndon@nexus.ca writes:
%
%One problem with this is that cron jobs don't go through login. Yes I can
%add an explicit ulimit command to the command lines in cron, just as I
%can add wrappers around login. The fact that I have to do this on such
%a global scale argues that perhaps this limit shouldn't be there in the
%first place ...

Ok -- so the obvious solution is to write a new /etc/init that
sets the ulimit and then execs the real init, "/etc/init.real".
Then every process on the system inherits the big ulimit.
(I haven't had the guts to try this, however)
-- 
Steve Losen     scl@virginia.edu
University of Virginia Academic Computing Center