Xref: utzoo comp.unix.i386:2376 comp.unix.wizards:20204
Path: utzoo!utgpu!jarvis.csri.toronto.edu!cs.utexas.edu!samsung!think!husc6!m2c!jjmhome!junkyard!joe
From: joe@junkyard.UUCP (Joseph Sarkes)
Newsgroups: comp.unix.i386,comp.unix.wizards
Subject: Re: "bad ulimit" on all non-root "at" & "batch" jobs under 386/ix
Summary: ulimit
Message-ID: <618@junkyard.UUCP>
Date: 17 Jan 90 23:02:59 GMT
References: <558@hades.OZ>
Followup-To: poster
Lines: 11


ulimit is set by the kernel for all programs using the compiled in
value. This is set in the configuration file (stune) or whatever
your system uses. since login runs as root, it can take the default
value and raise it. a process started by cron is not started by
login, thus it does not get its ulimit raised before running. thus
is is necessary to have the stune value of ulimit as high or higher
than the default login value for cron to work right, or you can
change the cron prototype if that works better for you. 

Joseph Sarkes	(junkyard!joe)