[Bug 1398] DHCP server stops unexpectedly after less then 24 hours

[drift@skolelinux.org]

http://bugs.skolelinux.org/show_bug.cgi?id=1398


José L. Redrejo Rodríguez <jredrejo@edu.juntaextremadura.net> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |jredrejo@edu.juntaextremadur
                   |                            |a.net




--- Comment #7 from José L. Redrejo Rodríguez <jredrejo@edu.juntaextremadura.net>  2009-12-16 14:06:30 ---
Why do you recommend the cronjob?
If you add  new machines using lwat, you need to restart the daemon (exactly as
we did in etch when dhcpd.conf was modified).
Also, you need to restart powerdns if the machine has a dns entry.
If you don't add new machines you don't need to restart the daemon.
So adding the cronjob would just imply telling the users that new machines are
not available until next day (or next hour, or next minute, depending on the
cron setup, but I don't think restarting the daemon every minute is a good
idea).

Isn't it easier keeping the etch documentation?: after adding new machines
(modifying dhcpd.conf or using lwat) you need to restart the daemon.

Mi 20 cts


-- 
Configure bugmail: http://bugs.skolelinux.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
You are watching all bug changes.