Linux - NewbieThis Linux forum is for members that are new to Linux.
Just starting out and have a question?
If it is not in the man pages or the how-to's this is the place!
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Introduction to Linux - A Hands on Guide
This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter.
For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own.
Click Here to receive this Complete Guide absolutely free.
This script runs forever - doesn't it make more sense to create a simpler script that is run as a cron job? Then you will have much better control about the timing intervals. Your script won't eat a lot of system resources, but it's just bad practice to use endless loops with sleep calls.
I'd also add that this is a poor approach to service management, IMO. If httpd is crashing regularly, diagnose and solve the problem. You should also deploy some form of service monitoring - e.g. Nagios.
Your script is causing a lot of unnecessary activity (and probably service interruptions) for the httpd daemon. A closely related question is: why is this script you're proposing necessary? Is httpd regularly crashing?
The one-liner I suggested could run as a cronjob every 5 minutes or so.
Like Anomie already said: if your httpd is crashing regularly combatting symptoms won't make the problem go away. You need to diagnose and solve the problem instead. Do your system and http daemon access and error logs show warnings or errors?