Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP Path: utzoo!utgpu!water!watmath!clyde!cbosgd!ihnp4!homxb!houxa!jph From: jph@houxa.UUCP Newsgroups: comp.sys.att Subject: Re: 3b2/400 ulimit Message-ID: <1720@houxa.UUCP> Date: Tue, 1-Dec-87 11:25:28 EST Article-I.D.: houxa.1720 Posted: Tue Dec 1 11:25:28 1987 Date-Received: Fri, 4-Dec-87 07:30:07 EST References: <226@tsc.UUCP> <901@csuchico.EDU> <2280@tut.cis.ohio-state.edu> <2445@tut.cis.ohio-state.edu> Organization: AT&T Bell Laboratories, Holmdel Lines: 49 Keywords: ULIMIT did not become tunable until SysV.3.1 - FAR too late Summary: Safer to replace getty In article <2445@tut.cis.ohio-state.edu>, karl@mumble.cis.ohio-state.edu (Karl Kleinpaste) writes: >> robby@eiibank.UUCP writes: >> My impression is that what is being discussed is the variable >> ULIMIT which is the maximum write size of a file. If so, then DO >> NOT mess with init. In SYS V version 2.something and later ULIMIT >> is a TUNABLE parameter. > > The max-file-size-limit is exactly what that script is supposed to > fix. In fact, that limit did not become a tunable until (*cringe*) > SysV.3.1; I have a SysV.3.0 3B2/400 called osu-cis which does not have > any reference to ULIMIT in its /etc/master.d/kernel. > > The script I posted is something I wrote 2 years ago when fighting > this problem every time I turned around (I am in the habit of having > to move very large files around with quite some frequency), and I > formalized it for myself and also sent it to Richard Stallman for > inclusion in the standard GNU Emacs distribution when I was doing SysV > compatibility things for that program; I picked up the copy I posted > here from just such a distribution. Although it is quite tunable in > The Right Way via /etc/master.d files in V.3.1, it took AT&T > altogether TOO LONG to figure this out, and in fact it was ridiculous > of them to have ever imposed the stupid 1Mb limit in the first place. > > So if you have V.3.1, please ignore the script I posted. If, however, > you are one of the vast, VAST majority of non-AT&T sites (and thus > cannot get V.3.1 practically for free) running V.3.0 or V.2.x.y.z.a.b, > then that script will do a very nice job of "fixing" your ulimit > problems. > -=- > Karl A much safer and more selective way to accomplish the same result is to replace references to getty to references to a program similiar to the one Karl proposed. The program should set ULIMIT to a higher value, and then exec the real getty. Simply use the new program in place of getty ONLY ON THE PORTS THAT NEED THE HIGHER ULIMIT (such as for uucp/news). I seem to remember a program distributed by AT&T a few years ago to 3B users (unlimit.c I think) that did the same thing. ------- Disclaimer: I hereby disclaim all my debts. ------ Jack Harkins @ AT&T Bell Labs Princeton Information (201) 949-3618 (201) 357-7573 ihnp4!houxa!jph