I’ve also thought about preserving the contents of dnsmasq,leases. Sometimes I scp that file to another machine before a BuC reboot then scp it back again (and “svi dnsmasq restart”) afterwards.
It’s not a huge issue to lose the DHCP leases themselves; mostly the pain comes from DNS not knowing about DHCP-allocated addresses (which dnsmasq takes care of automagically) after a router reboot, until the leases are renewed. Would adding a script to /etc/rc0.d/ work as a trigger to save the file - at least for a planned reboot? If the power dies then there’s not much you can do. I agree it would be overkill to re-save the file for every lease renewal. John’s comment about ntp.drift is a good one and there is other ‘runtime state’ that might benefit from being saved - e.g. vnstat traffic statistics. Arguably those settings are different from ‘static config’. davidMbrooke > On 24 Jan 2017, at 20:11, Erich Titl <erich.t...@think.ch> wrote: > > Hi > > Am 24.01.2017 um 15:35 schrieb John Sager: >> I think he wants to save it before every reboot rather than manually. > > In the end that is the same, you need to know how to save the config. > > You could do that every time a new lease is granted but I think that > this would be a pretty heavy operation. If you need this for statistical > stuff then it would be easier to log the leases somewhere else. Actually > I would not know what else you need the file for. > > cheers > > ET ------------------------------------------------------------------------------ Check out the vibrant tech community on one of the world's most engaging tech sites, SlashDot.org! http://sdm.link/slashdot ------------------------------------------------------------------------ leaf-user mailing list: leaf-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/leaf-user Support Request -- http://leaf-project.org/
