Run monit on it and restart the fuckers when they aren't playing nicely. Here's a sample of my old monit config that did just that: http://pastie.org/287363
...OR switch to mod_rails. I just made the switch and I'm loving not having to slap my mongrels around or deal with monit madness anymore. -------------------- seth - subimage llc ----- http://sublog.subimage.com ----- Cashboard - Estimates, invoices, and time tracking software - for free! http://www.getcashboard.com ----- Substruct - Open source RoR e-commerce software. http://code.google.com/p/substruct/ On Tue, Oct 7, 2008 at 6:26 PM, Anthony Ettinger <[EMAIL PROTECTED]> wrote: > > PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ PPID > COMMAND > 12565 ettinger 39 0 1110m 1.1g 2680 R 99.9 54.4 21:53.77 1 > /usr/bin/ruby1.8 /usr/bin/mongrel_rails start -C > /home/ettinger/directoryofdirect > > > > CPU: 99.9% > Mem: 54.4% > > What can I do to bring this back inline with an acceptable value? > > > -- > Anthony Ettinger > 408-656-2473 > http://anthony.ettinger.name > > > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Deploying Rails" group. To post to this group, send email to rubyonrails-deployment@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/rubyonrails-deployment?hl=en -~----------~----~----~----~------~----~------~--~---
