Thanks. Monitoring apache won't help so I guess I'll have to write my own script to extend god?
In the script I can do a "ps -o pid,pcpu,comm -u username" to output each process owned by the user, and then I'll parse it looking for any ruby process taking up 100% cpu. If this is true for x cycles, I'll kill it. I found this post for reference: http://groups.google.com/group/god-rb/browse_thread/thread/616935815a94f701 Am I on the right track? If so please let me know and I'll post the result when I'm done. On Mar 22, 5:31 am, Ramon Tayag <[email protected]> wrote: > Isn't THE answer but this will help you: > > http://groups.google.com/group/phusion-passenger/browse_thread/thread... > > Ramon Tayag > > > > On Sun, Mar 22, 2009 at 10:23 AM, lampy <[email protected]> wrote: > > > I have been having a few stray ruby processes take up 100% cpu with > > Apache and passenger (modrails). > > > Can anyone please give me some tips on how I can watch for this, since > > they don't have any pids? I would simply like to kill the specific > > ruby process, but I suppose a killall would do the trick as well. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "god.rb" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/god-rb?hl=en -~----------~----~----~----~------~----~------~--~---
