-- Mark <[EMAIL PROTECTED]> wrote (on Friday, 22 June 2007, 02:09 AM +0100): > I'd like to suggest a quick and dirty one liner solution to ease the pain. > Something like this in the server's root crontab: > > 0,15,30,45 * * * * result=`wget --tries 1 --server-response --timeout 60 > http://framework.zend.com/wiki/display/ZFDEV/Home 2>&1 | grep 'HTTP/'`; [[ > ${result} == " HTTP/1.1 200 OK" ]] || ( echo "Wiki site down. ${result} > reported. Attempting restart"; /etc/init.d/apache2 restart )
While I too feel your pain (I have to work with confluence and jira regularly), the problem is that it's not as simple as that. These tools run off of Tomcat, and need to be shut down in a particular order, and restarted in a particular order as well. Additionally, they don't always shut down correctly, which is a condition that can only be corrected by manual intervention. An automated script such as this could actually do more damage than good. Be assured, the framework team does have this issue as a priority prior to the 1.0.0 release; it's just a matter of time. -- Matthew Weier O'Phinney PHP Developer | [EMAIL PROTECTED] Zend - The PHP Company | http://www.zend.com/
