"bad ulimit" on all non-root "at" & "batch" jobs under 386/ix
greyham at hades.OZ
Wed Jan 17 06:37:11 AEST 1990
Our system has suddenly, and for no apparent reason, started rejecting all
jobs from "at" and "batch" by users other than root with the error message
"bad ulimit" mailed back to the user when the command is run.
The problem appears to be in setting up the batch environment to be the
same as the one in which the job was queue'ed. Our /etc/default/login
(to make filesize effectively unlimited).
Then, the /usr/lib/cron/.proto file has an entry:
(to set the ulimit the same as when the batch job was queued).
But, when this 'ulimit' command is ultimately run in the batch job, it
gets rejected with the "bad ulimit" message. Only root can increase it's
ulimit; so presumably cron should be starting the jobs with unlimited
(or very large) ulimit, so that the .proto generated entry can bring it
down to what it should be. So, what could be causing cron to start the job
with too small a ulimit?. Or is something else wrong here?. Any ideas?.
/* Greyham Stoney: Australia: (02) 428 6476 *
* greyham at hades.oz - Ausonics Pty Ltd, Lane Cove, Sydney, Oz. *
* ISDN: Interface Subscribers Don't Need */
More information about the Comp.unix.i386