Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!utgpu!water!watnot!watmath!clyde!rutgers!dayton!meccts!nis!pnessutt
From: pnessutt@nis.UUCP
Newsgroups: comp.unix.questions
Subject: Re: "at" command doesn't work after increasing ulimit, HELP Please!
Message-ID: <265@nis.UUCP>
Date: Sat, 4-Apr-87 23:26:34 EST
Article-I.D.: nis.265
Posted: Sat Apr  4 23:26:34 1987
Date-Received: Sun, 5-Apr-87 22:42:53 EST
References: <169@osupyr.UUCP>
Reply-To: pnessutt@nis.UUCP (Robert A. Monio)
Organization: National Information Systems, Inc., Minneapolis
Lines: 29
Keywords: ulimit

In article <169@osupyr.UUCP> jdc@osupyr.UUCP (Jim D Corder) writes:
>
>	We have increased our ulimit on our AT&T 3B2/300 70meg 2meg machine
>with the following C program /bin/login.  The original /bin/login was moved
>to /bin/login2:  The program works.
>

We had a similar problem with a 3B2-400 that we had.  Our ULIMIT was
set for 1 meg.  To get around this we used a shell script that set the
ULIMIT up before getty was called.  It looked like this:

   /etc/biggetty :
   
     ulimit 4096
     /etc/getty $1 $2

All that was needed was to make a change to /etc/inittab to call
biggetty with the parameters of the tty# and the baud rate.  This
script worked fine for us.  Now we have a NCR Tower 32 and a XP.  We
don't need it on these machines.
 
-Bob


-- 
 Robert A. Monio                              UUCP: ihnp4!meccts!nis!pnessutt
 Systems/Analyst - Technical Services         ATT: (612) 894-9494
 National Information Systems, Inc.
                      "These Proceedings are Closed!"