Thanks Richard, was thinking of doing that but was wondering if there was an existing solution, one built into Mongrel perhaps.
Niall Mullally [EMAIL PROTECTED] wrote: > You could write init.d script to check if those files exist and if so > delete them before trying to start up the cluster. > - Richard > > On May 21, 3:46 am, Niall Mullally <[EMAIL PROTECTED]> wrote: >> Hi, >> One of my site's servers had a problem yesterday and the host >> restarted it. During boot up Mongrel failed to start as the PID files >> still existed in /log >> >> I didn't find out about this reboot until several hours later so the >> site was down that entire time which is less than ideal. >> >> Does anybody know of a way around this? Is there a built in way to >> force Mongrel to start and overwrite any existing PID files? >> >> I have the mongrel_cluster startup script setup correctly btw. >> >> Thanks in advance. >> >> Regards, >> >> Niall Mullally > > > > > -- Niall Mullally 4L Communications Ltd. http://www.4L.ie/ --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
