Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!tut.cis.ohio-state.edu!rutgers!bellcore!texbell!killer!rpp386!jfh
From: jfh@rpp386.Dallas.TX.US (John F. Haugh II)
Newsgroups: comp.bugs.sys5
Subject: Re: ulimit -- You don't need sources!
Summary: You don't need to write jillions of wrappers either!!!
Message-ID: <16463@rpp386.Dallas.TX.US>
Date: 5 May 89 23:03:36 GMT
References: <836@twwells.uucp> <4428@ihuxz.ATT.COM> <545@aurora.AthabascaU.CA> <5627@xyzzy.UUCP> <1153@unh.UUCP>
Reply-To: jfh@rpp386.Dallas.TX.US (John F. Haugh II)
Organization: River Parishes Programming, Dallas TX
Lines: 16

In article <1153@unh.UUCP> pss@unh.UUCP (Paul S. Sawyer) writes:
>In article <5627@xyzzy.UUCP>, duncan@rtp48.dg.com (W. Lee Duncan) writes:
>> Simply move /bin/login to, e.g. /usr/lib/old_login (and make it non-setuid).
>> Then, create a new /bin/login program (which will be setuid to root):
>> 
>Since INIT is running as root anyway, it can set the ulimit and then call
>getty.  E.g., in /etc/inittab:
>
>t000:2:respawn:/etc/gettyup tty000 9600

No - since UNIX forks init directly out of the kernel as root, why
not step in there and raise the ulimit before the real init gets to
run?

Now you only have one wrapper instead of all the getty, login, cron,
and what-else-have-you versions.