Note that, depending on the resource being limited, ulimit may cause
the process to crash or shut down when that resource hits the limit.

-- 
Raul

On Fri, Dec 2, 2022 at 9:54 AM David Lambert <b49p23t...@gmail.com> wrote:
>
> To avoid this situation is it possible to limit memory and cpu time on
> the process?
>
> bash provides ulimit, maybe DOS has similar facility.  That said, I've
> not gotten ulimit to work as I expect and instead increased my
> computer's RAM.  Then when I suspect there might be trouble I monitor
> the system and manually kill errant process before it gets to the paging
> state.  When I was even newer with j I was pretty good at writing
> sentences that would, given opportunity, consume all the memory in the
> world.
>
> > Date: Fri, 2 Dec 2022 10:53:04 +0000
> > From: Richard Donovan<rsdono...@hotmail.com>
> > To: J Programming<programm...@jsoftware.com>
> > Subject: [Jprogramming] Avoiding J crash
> > Message-ID:
> >       
> > <cwxp123mb5250709d8d2e91951811c6fbbd...@cwxp123mb5250.gbrp123.prod.outlook.com>
> >
> > Content-Type: text/plain; charset="Windows-1252"
> >
> > Hi!
> >
> > Is there any way to avoid the situation whereby by  error I put J into an 
> > infinite loop from which the only recovery is to reboot my Windows laptop?
> >
> > I guess that my erroneous routine is locking the CPU to such a such an 
> > extent that I can’t even get to run Jbreak.
> >
> > I quite often receive a recoverable situation when a limit has been 
> > exceeded but if I get the infinite loop situation I have lost my entire 
> > session and have to start again.
> >
> > I really need a global setting which limits the amount of cpu usage and 
> > aborts a function before it gets out of hand.
> >
> > Thanks,
> >
> > Richard
> ----------------------------------------------------------------------
> For information about J forums see http://www.jsoftware.com/forums.htm
----------------------------------------------------------------------
For information about J forums see http://www.jsoftware.com/forums.htm

Reply via email to