I hope someone chimes in with a better idea, because my ideas involve some
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 can't have 'at' jobs, I don't know what to try.
Of two proposed above, cron is the better. It will survive a reboot nicely,
wait its waiting period, and start your webkit. With 'at', I don't know the
behavior across a reboot that takes the machine out of commission past the
start time of the job.
David Hancock | dhancock@... | 410-266-4384
From: Ben Logan [mailto:ben@...]
Sent: Saturday, January 25, 2003 6:12 AM
Subject: [Webware-discuss] Keeping Webware running.
I am running Webware on a shared Linux web server (I don't have root
priveleges), and am wondering what I can do to make certain that it
stays running. I've been starting the appserver by logging in via
ssh, and running 'nohup Appserver &', and that works, but sometimes it
dies for no apparent reason. I also need a way to make sure that it
gets restarted if they reboot the server. I am hoping for a solution
that doesn't involve the server admins installing Webware system wide.
Has anyone else solved this problem?
Google Answers Researcher
When you're searching for information, Google Answers.
This SF.NET email is sponsored by:
SourceForge Enterprise Edition + IBM + LinuxWorld = Something 2 See!
Webware-discuss mailing list