cron job for checkingrestarting a service
You should probably find out why it stops running, because that very fact is telling you something is wrong. When one thing is wrong and you do not know what it is, it should be a warning that you cannot trust your process, so you better fix it.
Sure there is, but if you are unwilling to find the problem, why wait for a cron job to fix it. Why not start it inetc-inittab with a line something like this:
In the Usenet newsgroup comp.os.linux.misc, in article Does it still answer to that? sunsite.unc.edu became metalab.unc.edu, and is now ibiblio.org. -rw-rw...
fmc:2345:respawn:-opt-IBM-db2-V8.1-bin-db2fmcd -------
This is a real line from myetc-inittab for a process that must always run. Of course, you must be root to put such a thing into the inittab.
But I seriously suggest you not do this, but find the real problem instead. The process must be exiting for a reason, and you should look in a suitable logfile to see what that might be. First place to look isvar-log-messages, but it could be somewhere else up there.
-- .~. Jean-David Beyer Registered Linux User 85642. V PGP-Key: 9A2FC99A Registered Machine 241939. ^^-^^ 21:55:00 up 55 days, 15:49, 3 users, load average: 3.30, 3.34, 3.21
DNS ppp0 glitch with lynx on tomsrtbtFIXED 4448
Linux groups from Newsgroups