Maybe it’s better to always validate the config before you restart dnsmasq. Such ‘failsafe’ config options tend to be used ‘just in case’, leading to silent failure when a config error does occur. TFTP probably has such a limited feature set that faulty functioning can be easily detected by the user. I don’t think that’s true for e.g. DHCP.
Sent from mobile > Op 23 mei 2021 om 12:09 heeft Ercolino De Spiacico <bellocar...@hotmail.com> > het volgende geschreven: > > > I have recently been locked out of my remote router(s) because I made a typo > on the dnsmasq config (e.g. as a syntax of dhcp-host, or similar), this > resulted in dnsmasq unable to (re)start and exiting with a configuration > parsing error something. My mistake indeed but... does it really have to > crash the whole dnsmasq? > > I know that the internal dnsmasq's tftp server supports already a safe mode > to run via the tftp-no-fail > > So could the whole dnsmasq have a no-fail feature e.g. just log+ignore the > part of config not understood? > > Thanks > _______________________________________________ > Dnsmasq-discuss mailing list > Dnsmasq-discuss@lists.thekelleys.org.uk > https://lists.thekelleys.org.uk/cgi-bin/mailman/listinfo/dnsmasq-discuss
_______________________________________________ Dnsmasq-discuss mailing list Dnsmasq-discuss@lists.thekelleys.org.uk https://lists.thekelleys.org.uk/cgi-bin/mailman/listinfo/dnsmasq-discuss
