Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!cornell!rochester!rutgers!att!mcdchg!ddsw1!corpane!brooks
From: brooks@corpane.UUCP (David E. Brooks Jr)
Newsgroups: comp.bugs.sys5
Subject: Re: ulimit -- You don't need sources! (kind of long)
Summary: Try it with init . . .
Keywords: sources, C
Message-ID: <601@corpane.UUCP>
Date: 5 May 89 13:13:03 GMT
References: <836@twwells.uucp> <4428@ihuxz.ATT.COM> <545@aurora.AthabascaU.CA> <6218@cbnews.ATT.COM>
Distribution: usa
Organization: Corpane Industries, Inc., Louisville Ky
Lines: 21

In article <6218@cbnews.ATT.COM>,
   grs@cbnews.ATT.COM (gregg.r.siegfried) writes:
> The problem I've always had with this
> is that all user processes (or the ones in your "database") have a higher
> ulimit, while all the non-login processes retain the 1K ulimit.

I saw a posting not that long ago where someone (I wish I could remember
who) did a similar process using init.  This way, all processes (which are
sub-processes of init, eventually) would have the higher ulimit.  It would
seem to me that combining the two methods would provide a reasonably powerful
method of controlling file sizes, since there is no reason that the pseudo-
login couldn't lower the ulimit.

> Gregg Siegfried
> Speaking for myself, of course..

-- 
David E. Brooks Jr                           UUCP :  ...!ddsw1!corpane!brooks
Corpane Industries Incorporated                      ...!ukma!corpane!brooks
10100 Bluegrass Parkway                      Phone:  +1 502 491 4433 x122
Louisville, KY  40299                        Quote:  printf("%c",34)