I didn't try but I suppose the --test parameter works. However this is
not my point.
I would like dnsmasq to stop (prevent execution) only for very serious
matters like incomplete IP addresses in config, binding port higher than
65K, etc. you name it.
I believe there is a rather long list of reasons (incorrect dhcp-host
syntax being one as per original message) that could/should be excluded
from this process execution control.
This takes nothing away from the fact that having a clear/clean config
is ultimately a must, I just don't want to have to call a person in a
different continent again because of a typo on a "secondary"
configuration parameter.
In one sentence: let's make dnsmasq as resilient as possible.
Thanks
On 23/05/2021 20:07, Lonnie Abelbeck wrote:
On May 23, 2021, at 12:47 PM, Cyberfusion <wedwa...@cyberfusion.nl> wrote:
Op 23 mei 2021 om 19:31 heeft Lonnie Abelbeck <li...@lonnie.abelbeck.com> het
volgende geschreven:
On May 23, 2021, at 11:08 AM, Cyberfusion <wedwa...@cyberfusion.nl> wrote:
Maybe it’s better to always validate the config before you restart dnsmasq.
# dnsmasq --test
dnsmasq: syntax check OK.
Then the solution is to fix config validation, not add an option to ignore
errors.
I was just indicating dnsmasq had a validation test, builtin.
Best if the original reporter (Ercolino) could recreate the syntax error and
see if --test flags it.
Lonnie
_______________________________________________
Dnsmasq-discuss mailing list
Dnsmasq-discuss@lists.thekelleys.org.uk
https://lists.thekelleys.org.uk/cgi-bin/mailman/listinfo/dnsmasq-discuss
