It might be easiest to obtain that information from within the script that actually restarts the process.
For example if you are using an init script, dump the data you wish to know from the restart section. But even then you only know the data at the time just before the restart. To really know what is going on, you should monitor your processes more closely. I advice using collectd or another form of logging the state of your processes. And you can send an email if your process reaches for example 80MB you don't have to transition to another state. For example from within the lifecycle section of a watch. The version of god that I use (0.11.0) however needed a patch keep the lifecycle conditions between states. On Apr 9, 11:13 pm, Ran Margaliot <[email protected]> wrote: > Hello, > > I am using god to monitor my delayed jobs. > currently I suffer from exceeded memory consumption from time to time, > ive set god to restart jobs exceeding 100MB. > my question is: is there a way to get information from the current > running job before god restarts it? > this is crucial in order to know what process exactly causes the > exceeded memory consumption > > Thanks, > > Ran -- 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.
