On Friday, 17 January 2003 at  5:06:56 +0900, Jim Freeze wrote:
> On Friday, 17 January 2003 at  1:21:02 +0900, Richard Kilmer wrote:
> > That works wonders.
> > 
> > When you set that limit is it once and for all?
  
  This is all I know so far.

  
You could add to the shell start-up file or to your ruby program

ulimit -s 8192


"The limit man page is effectively in the tcsh man page since it is a 
shell built-in command:"

"       limit [-h] [resource [maximum-use]]
                Limits  the consumption by the current process and
                each process it creates to not individually exceed
                maximum-use on the specified resource.  If no max?
                imum-use is  given,  then  the  current  limit  is
                printed; if no resource is given, then all limita?
                tions are given.  If the -h  flag  is  given,  the
                hard  limits  are used instead of the current lim?
                its.  The hard limits impose a ceiling on the val?
                ues  of  the  current limits.  Only the super-user
                may raise the hard limits, but a user may lower or
                raise the current limits within the legal range.

                Controllable  resources  currently include cputime
                (the maximum number of cpu-seconds to be  used  by
                each  process),  filesize (the largest single file
                which  can  be  created),  datasize  (the  maximum
                growth of the data+stack region via sbrk(2) beyond
                the end of the program text), stacksize (the maxi?
                mum   size  of  the  automatically-extended  stack
                region), coredumpsize (the  size  of  the  largest
                core  dump  that  will be created), and memoryuse,
                the maximum amount of physical  memory  a  process
                may have allocated to it at a given time.

                maximum-use  may  be given as a (floating point or
                integer) number followed by a scale  factor.   For
                all limits other than cputime the default scale is
                `k' or `kilobytes' (1024 bytes); a scale factor of
                `m'  or `megabytes' may also be used.  For cputime
                the default scaling is `seconds',  while  `m'  for
                minutes  or  `h'  for hours, or a time of the form
                `mm:ss' giving minutes and seconds may be used.

                For both resource names and scale  factors,  unam?
                biguous prefixes of the names suffice."



-- 
Jim Freeze
----------
"I hate it when my foot falls asleep during the day cause that means
it's going to be up all night."
		-- Steven Wright