On Thu, May 24, 2018 at 4:16 PM e9hack wrote:
> Am 24.05.2018 um 09:16 schrieb Hans Dedecker:
> >> possible and must not load hostfiles from other instances. The entry in
> >> dnsmasq.init must be:
> >
> >> xappend "--addn-hosts=$HOSTFILE"
> > Making such a change will break
Am 24.05.2018 um 09:16 schrieb Hans Dedecker:
>> possible and must not load hostfiles from other instances. The entry in
>> dnsmasq.init must be:
>
>> xappend "--addn-hosts=$HOSTFILE"
> Making such a change will break the host entries learned via odhcpd as the
> entires are put into the odhcpd
On Wed, May 23, 2018 at 11:43 PM e9hack wrote:
> Hi,
> this commit and the way, who the init script handles hostfiles seams to
be completely wrong. The init script generates
> one independent hostfile per dnsmasq instance and writes it to a common
directory. Multiple dnsmasq
Hi!
On Wed, May 23, 2018 at 11:43:31PM +0200, e9hack wrote:
> Hi,
>
> this commit and the way, who the init script handles hostfiles seams to be
> completely wrong. The init script generates
> one independent hostfile per dnsmasq instance and writes it to a common
> directory. Multiple dnsmasq
Hi,
this commit and the way, who the init script handles hostfiles seams to be
completely wrong. The init script generates
one independent hostfile per dnsmasq instance and writes it to a common
directory. Multiple dnsmasq instances are
possible and must not load hostfiles from other instances.