Hi Richard, One way is to use something like Nagios to monitor the "last-modified" time/date of Squid's access.log. If the file hasn't been updated/modified within, say, 30 minutes, Nagios considers that a problem and restarts the daemon. If doing things this way, be sure to take night-time activity (if any) into account when you set the "problem" number.
If you're running a 9-5 office you may want to completely disable this check during the night hours. If you don't have/don't want Nagios, there's a variety of other ways to accomplish the above including a bash script on a cronjob. Regards, Kyle Spencer ----- Original message ----- > Richard, > > I am no Linux guru, but what you need is a script that keeps checking > whether the squid daemon is up, and it restarts it when its not > > Stephen > > From: Richard Zulu [mailto:[email protected]] > Sent: Monday, October 18, 2010 1:13 PM > To: Linux Users Group Uganda > Subject: [LUG] Squid > > Hey, > > Been looking around in vain..does anyone know of a script that can > automagically start my squid daemon when the squid stops running? > > -- > Richard Zulu | Chief Executive Officer | Time Information Company | > www.time.co.ug | +256752624006 > > <http://www.time.co.ug/media/time_logo.jpg> > Disclaimer: Time Information Company cannot accept responsibility for > the security or accuracy of outgoing electronic mail. Any view or > opinions expressed are solely those of the author and do not represent > the view of the Time Company unless specifically stated. The > information contained in this e-mail may be subject to public disclosure > under your country's Legislation. Unless the information is legally > exempt from disclosure, the confidentiality of this e-mail, and your > reply cannot be guaranteed. _______________________________________________ LUG mailing list [email protected] http://kym.net/mailman/listinfo/lug LUG is generously hosted by INFOCOM http://www.infocom.co.ug/ All Archives can be found at http://www.mail-archive.com/[email protected]/ The above comments and data are owned by whoever posted them (including attachments if any). The List's Host is not responsible for them in any way. ---------------------------------------
