will dynamic dhcpd.conf be supported in future releases
Shane Kerr
Shane_Kerr at isc.org
Fri Aug 11 08:48:55 UTC 2006
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
jw354 wrote:
>
> What would this gain? I have had the experience of writing a script
> to stop and start dhcpd during production. To assure the
> processes didn't overlap (which for some daemons, can result in
> no pid file, among other things), I incorporated a loop that tests
> to see that the old process has gone away. Later I had to tune the
> sleep-length in the loop so our process monitor wouldn't alert
> us that there was no dhcpd process running. I'd love to do away with
> all
> that crap and have a clean way to start the new process immediately
> after the old one stops.
If this is your concern, you might be better of writing a wrapper script and
running dhcpd in non-daemon mode. Something like this:
- ---
#! /bin/sh
while true; do
/usr/sbin/dhcpd -f $*
done
- ---
Then to restart you can issue "killall dhcpd", or to stop you would kill the
wrapper script first, and then kill the dhcpd process.
- --
Shane
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
iD8DBQFE3ER2MsfZxBO4kbQRAsBYAJ946OZ33xnHpAX6GA3lvY9MPiKogACgrkNJ
CvbUrHsvv4x1vikF3qSvgkU=
=8EgE
-----END PGP SIGNATURE-----
More information about the dhcp-users
mailing list