Running a cron for god is probly a good idea anyway, as no one is watching god to make sure he doesn't get out of control or go away.
I suppose cron (time) is the ultimate master of daemons. Nathan On Jun 30, 2:24 am, zubin <[email protected]> wrote: > I run a very busy site and had similar problems with god. > Adding this cron task solved the problem: > > # Restarting god weekly at midnight > 0 0 * * 0 root god quit; sleep 1; killall -9 god; sleep 1; god -c / > home/deploy/rails_apps/g2/current/config/app.god > > On Jun 4, 4:58 am, J M <[email protected]> wrote: > > > > > Hi, I noticed that my God process steadily grows its RAM consumption. > > God has been running on my server for about a week and it has grown to > > 296m VIRT and 283m RES. Does anyone else see this with their God > > process? Is there a command to restart God without affecting the > > watches? > > > Thanks!, > > John --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
