From: King, Michael (MKing@bridgew.edu)
Date: Thu Jul 15 2004 - 13:53:53 CDT
Mike,
You might want to do a few things with your script.
First, when the server fails, and it reloads the original file. You
leave the dhcpd.conf.new file untouched. If the server failed to start
because of a directive that was added to dhcpd.conf.new, the next time a
registration is added to dhcpd.conf.new the process fails again.
Also, I'm not sure if sleep 1 was enough time. I seem to remember
needing a bit longer sleep time there.
-----Original Message-----
From: owner-netreg@southwestern.edu
[mailto:owner-netreg@southwestern.edu] On Behalf Of Mike Husmann
Sent: Thursday, July 15, 2004 2:37 PM
To: netreg@southwestern.edu
Subject: [PMX:23%] RE: NetReg: reliably restarting dhcpd
Keith,
I had the same problem. It happens when dhcpd doesn't start up, and
therefore, there is no pid file. So, I added a check for the existance
of the pid file before comparing it to the 'ps' command.
I have included a copy of the refresh-dhcpdconf script that I
customized. It also sets a flag (touches a file) if there is a problem,
so that if you customize your admin script, you can instantly notice if
something bad has happened. Feel free to use it, if it is any good to
you. If so, there are variables at the top that will probably need to
be customized for your installation.
Mike
**********************************************************************
To unsubscribe from this list, send an e-mail message to
majordomo@southwestern.edu containing a single line with the words:
unsubscribe netreg
Send requests for assistance to: owner-netreg@southwestern.edu
**********************************************************************
This archive was generated by hypermail 2.1.4 : Thu Aug 12 2004 - 12:01:46 CDT