On Sat, 2003-01-25 at 08:30, Hancock, David (DHANCOCK) wrote:
> I hope someone chimes in with a better idea, because my ideas involve some
> work...

Sadly there's not a much better solution included with Webware or that
I've used, though someone else may have a solution.

> If you have sufficient rights to have cron jobs, consider writing a little
> monitor that runs via cron.  It just needs to look for the appserver
> process, or retrieve a page using wget or lynx -dump, and if it can't get
> the page, run a script to restart webkit.
> 
> If you can't have cron jobs, but can have 'at' jobs, write the same monitor
> as for cron, but extend it slightly to resubmit itself via the 'at'
> mechanism when it completes.

If you aren't sure if you have cron access, just try "crontab -e", and
read "man 5 crontab" to learn about it.  If you find the AppServer isn't
running, you should be sure to kill it (-9) before restarting it, in
case it's not dead but not responding.

Hmm... might go something like:

# crontab:
*/10 * * * * $HOME/bin/checkwebware >> $HOME/bin/checkwebware.log 2>&1

# checkwebware:
wget http://localhost/WK -O - > /dev/null 2>&1
if [ "$?" != "0" ] ; then
    # wget failed
    killall -9 AppServer
    ~/Webware/WebKit/webkit start
fi


It'll take some testing to get this properly tweaked.


-- 
Ian Bicking           Colorstudy Web Development
[EMAIL PROTECTED]   http://www.colorstudy.com
PGP: gpg --keyserver pgp.mit.edu --recv-keys 0x9B9E28B7
4869 N Talman Ave, Chicago, IL 60625 / (773) 275-7241



-------------------------------------------------------
This SF.NET email is sponsored by:
SourceForge Enterprise Edition + IBM + LinuxWorld = Something 2 See!
http://www.vasoftware.com
_______________________________________________
Webware-discuss mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/webware-discuss

Reply via email to