Simon,<br><br>Would it be possible to add some logic to resync with the external database when SIGHUP is received?<br><br>I propose the following set of rules:<br>rerun external-script "init"<br>any lease in the external database, which does not match any mac address in the internal list, is added to the internal list (unless it has expired, then use external-script "del")
<br>any lease in the external database, which matches the MAC address in the internal list but a different IP address, is removed with external-script "del"<br>any lease in the external database, which matches both MAC address and IP address in the internal list, is updated with external-script "old"
<br>any lease in the internal list not found in the external database is added in the external database with external-script "add"<br><br>Would this be possible? Any complications or undesired behavior you can see?
<br><br>Right now, spanning tree protocol and its "learning" states are playing havoc with my external-script "init", because the postgresql server isn't reachable when dnsmasq starts. I'll work on a solution to that independently, but it would be really nice to be able to resync the external database any time connectivity is lost and then restored.
<br><br>Thanks,<br>Ben Voigt<br><br>