[chuck-users] implementing a "wait for signal with timeout"

[mike clemow]

Linux 2.6 w/ realtime-patched kernel.  I run a cluster of headless AMD
Athlon machines with ChucK on each.  Each machine only has 256mb of
RAM, however, and I'm not surprised about the fact that ChucK can use
it all.  When it happens, the machine starts spewing error messages to
the console (which I never saw until I looked at the output of the
monitor--i usually login via ssh), which prevents me from logging in
and killing the process.  It also prevents me from logging in via ssh.
 I want to send some of this output, which specifically mentions the
process named "chuck" and un-reclaimable memory, to you folks, but
it's going to be difficult to capture.

I wonder if there's a way to specify a memory quota for a process in
Linux.  If it tries to use more, it gets killed by the OS...  I'm
speculating here.

-mike

On Wed, Jun 10, 2009 at 3:45 AM, Hans Aberg<haberg at math.su.se> wrote:
> On 10 Jun 2009, at 04:58, mike clemow wrote:
>
>>> Aren't you on a POSIX machine, so you can kill it by 'kill -9 <pid>'
>>> where
>>> <pid> is what you get from
>>>  ps -x | grep 'chuck'
>>
>> Can't even get a console!  :(
>
> What might this mean? What platform are you on?
>
>  Hans
>
>
>



-- 
http://michaelclemow.com
http://semiotech.org