Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!crdgw1!uunet!virtech!cpcahil
From: cpcahil@virtech.uucp (Conor P. Cahill)
Newsgroups: comp.unix.questions
Subject: Re: sh: Bad ulimit with atjobs
Message-ID: <1991Apr01.153443.13455@virtech.uucp>
Date: 1 Apr 91 15:34:43 GMT
References: <26413@adm.brl.mil>
Organization: Virtual Technologies Inc.
Lines: 24

wolf@grasp1.univ-lyon1.fr (Christophe Wolfhugel) writes:

>I have a strange behavior with at on a SVR3.2: when I use at jobs
>none gets executed and I have return code sh: Bad ulimit.

This problem is cause by the fact that you changed your ulimit in 
/etc/default/login, but did not change it in /etc/conf/cf.d/stune.  
Therefore cron starts with a lower ulimit than users whom login.

When your job is run, you as a normal user, cannot increase the ulimit
beyond what cron has it set to, so you get the error.

There are two ways to fix this.

	1. do it the right way-> change /etc/conf/cf.d/stune, rebuild /unix
	   and reboot 

	2. modify /etc/rc*.d/*cron to set the ulimit before the 
	   cron process is started.

-- 
Conor P. Cahill            (703)430-9247        Virtual Technologies, Inc.
uunet!virtech!cpcahil                           46030 Manekin Plaza, Suite 160
                                                Sterling, VA 22170