[comp.unix.questions] ulimit error on at/batch commands

bander@cs.odu.edu (James Bander) (07/19/89)

I am unable to use either the batch command or the at command.  Using either
one results in a mail message with something to the effect of:

     -sh:   bad ulimit

Can anyone shed any light on the problem?   I am running AT&T UNIX V/386 3.2
on an AT&T 6386E WGS.  The system has only been up for a few weeks; as far as
I know, we have always had this problem.   

-- 
-----------------------------------------------------------------------------
Jim Bander, Tidewater Consultants, Inc., Virginia Beach, VA
    
                                          Internet:  bander@cs.odu.edu
                                          Ma Bell:   (804) 497-8951
                                          USnail:    160 Newtown Rd. #415
                                                     Va. Beach, VA 23462

"The presence of humans, in a system containing high-speed electronic
computers and high-speed, accurate communications, is quite inhibiting." 
                                                 --Stuart L. Seaton, 1958
-----------------------------------------------------------------------------
Disclaimer:  All my mistaken opinions are my own.

funk@osiris.cso.uiuc.edu (07/22/89)

>/* Written 10:59 pm  Jul 18, 1989 by bander@cs.odu.edu in osiris.cso.uiuc.edu:comp.unix.questions */
>/* ---------- "ulimit error on at/batch commands" ---------- */
>I am unable to use either the batch command or the at command.  Using either
>one results in a mail message with something to the effect of:
>
>     -sh:   bad ulimit
>
>Can anyone shed any light on the problem?   I am running AT&T UNIX V/386 3.2
>on an AT&T 6386E WGS.  The system has only been up for a few weeks; as far as
>I know, we have always had this problem.   
>
We had the same problem on a unisys 5000/80 running SYSV.2.
We solved our problme by discovering that the ulimit was in effect during
the execution of the /etc/rc shell.  When cron was kicked off, it inherited
the default ulimit, so that every job that was kicked off (except root's)
failed when it attempted to raise the ulimit back to what it was when the
at command was executed.  (since root is the only one who can raise its ulimit)
When we added a line such as  ulimit 100000 before the startup of cron in 
/etc/rc,  this  had the effect of everyone LOWERING their ulimit, and everyone
worked OK


-------------------------------------------------------------------------------
|        Bruce Funk                         INTERNET: funk@osiris.cso.uiuc.edu |
|ACSEH, 21st TAACOM          __________________________________________________|
|Kaiserslautern, W. Germany  | Any resemblance between me and reality          |
|(guesting on osiris)        | is strictly coincidental                        |
-------------------------------------------------------------------------------