Am Sun, 23 May 2021 22:25:28 +0200
schrieb Geert Stappers via Dnsmasq-discuss
:
> I learnt it is already implemented
It is not. What they implemented, probably by doing copy from sysv, does
not help at all. There is zero need to run dnsmasq --test in this context,
dnsmasq will fail either
On Sun, May 23, 2021 at 09:01:01PM +0200, Cyberfusion wrote:
> Op 23 mei 2021 om 20:17 heeft Ercolino de Spiacico het volgende geschreven:
> >
> > 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
Allow me to disagree with your statement. It is not the software but the
developer defining the criticality.
We have the full list of parameters at this page:
https://thekelleys.org.uk/dnsmasq/docs/dnsmasq-man.html
All it needs is a categorisation for each parameter as in critical or
not as
> Op 23 mei 2021 om 20:17 heeft Ercolino de Spiacico
> het volgende geschreven:
>
> 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
On Sun, May 23, 2021 at 07:47:02PM +0200, Cyberfusion wrote:
> Op 23 mei 2021 om 19:31 heeft Lonnie Abelbeck het volgende geschreven:
> > On May 23, 2021, at 11:08 AM, Cyberfusion wrote:
> >> bellocarico:
> >>> ... idea for improvement on dealing with misconfiguration ...
> >>
> >> Maybe it’s
> On May 23, 2021, at 12:47 PM, Cyberfusion wrote:
>
>> Op 23 mei 2021 om 19:31 heeft Lonnie Abelbeck
>> het volgende geschreven:
>>
>>> On May 23, 2021, at 11:08 AM, Cyberfusion wrote:
>>>
>>> Maybe it’s better to always validate the config before you restart dnsmasq.
>>
>> # dnsmasq
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
> Op 23 mei 2021 om 19:31 heeft Lonnie Abelbeck het
> volgende geschreven:
>
>
>> On May 23, 2021, at 11:08 AM, Cyberfusion wrote:
>>
>> Maybe it’s better to always validate the config before you restart dnsmasq.
>
> # dnsmasq --test
> dnsmasq: syntax check OK.
Then
> On May 23, 2021, at 11:08 AM, Cyberfusion wrote:
>
> Maybe it’s better to always validate the config before you restart dnsmasq.
# dnsmasq --test
dnsmasq: syntax check OK.
Lonnie
___
Dnsmasq-discuss mailing list
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
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
11 matches
Mail list logo
