Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!mnetor!uunet!seismo!sundc!pitstop!sun!oliveb!jal
From: jal@oliveb.UUCP (Benjamin G. Golding)
Newsgroups: comp.unix.wizards,comp.unix.questions
Subject: Re: How to set ulimit in SysV
Message-ID: <6497@oliveb.UUCP>
Date: Tue, 6-Oct-87 09:52:44 EDT
Article-I.D.: oliveb.6497
Posted: Tue Oct  6 09:52:44 1987
Date-Received: Fri, 9-Oct-87 06:46:39 EDT
References: <1408@dasys1.UUCP> <6475@brl-smoke.ARPA> <6502@brl-smoke.ARPA> <275@minya.UUCP>
Organization: Olivetti ATC; Cupertino, Ca
Lines: 22
Keywords: patch ulimit
Summary: but it doesn't help cron
Xref: mnetor comp.unix.wizards:4724 comp.unix.questions:4420

In article <275@minya.UUCP>, jc@minya.UUCP (jc) writes:
> OK, I decided to see how hard this one was; it took 15 minutes, of which
> 13 were due to a bug in init....
> 
> What you do is change your inittab entries for getty to:
> 
> 	t3:2:respawn:/bin/sh /etc/Getty tty03 tty03

No.  This does not alter the ulimit for processes like cron and the
jobs that it starts up.

This really is terribly broken and a major oversight by AT+T.  I have
had trouble with this in a numer of different ways, such as
accidentally setting it to -1 and not being able to login because
/etc/login can't write /etc/utmp!  Can you believe they made it
signed?!  At least it's configurable in rel 3.1, though silly that you
can't turn it off.

	Ben Golding.
-- 
"Holy oleo, Batman!!"
"Why Boy Wonder; I didn't know you could yodel!"