[Dnsmasq-discuss] dhcp-script: environment var DNSMASQ_INTERFACE not always set

cript.d/10dhcpscript' root@F36-stube:~ dnsmasq --version Dnsmasq version 2.89 Copyright (c) 2000-2022 Simon Kelley ... Maybe somebody has an idea why this can happen, looking through the source it is not obvious and *should not happen* 8-) => except 'data.interface' is unknown. This hap

Re: [Dnsmasq-discuss] problem with loopback and 2.77test5

* Simon Kelley [10.05.2017 15:05]: > I wonder if this is to do with the extension of the ping-test to more > cases. Please could you try adding > > no-ping > > to the config, and see if that improves things? thank you - yes, that works...now the log shows:

[Dnsmasq-discuss] problem with loopback and 2.77test5

here the relevant things with recent lede-project.org root@box:~ dnsmasq -v Dnsmasq version 2.77test5 Copyright (c) 2000-2016 Simon Kelley Compile time options: IPv6 GNU-getopt no-DBus no-i18n no-IDN DHCP no-DHCPv6 no-Lua TFTP no-conntrack no-ipset no-auth no-DNSSEC no-ID loop-detect inotify #

Re: [Dnsmasq-discuss] dhcp-script and concurrency/parallel execution

* Nicolas Cavallari nicolas.cavall...@green-communications.fr [08.06.2015 19:58]: This is already the current behavior (helper.c:455). If you see lots of dhcp-script running, then you have another problem, probably bugs in your dhcp-script. Does it fork or run background commands ? i

[Dnsmasq-discuss] dhcp-script and concurrency/parallel execution

there is nothing about this issue in the docs or in the archive, so i will ask you. i have seen a lot of running instances of dhcp-script on an embedded box (OpenWrt, 2.73rc8). this is a problem in 2 ways: 1) memory consumption 2) concurrency, because we read/write into files with the same

Re: [Dnsmasq-discuss] problem with not executed /etc/dhcp-script.d/10dhcpscript

* Simon Kelley si...@thekelleys.org.uk [08.05.2015 22:36]: Are you sure the low-memory thing is relevant? Do you see the same problem on a newly booted machine? i'am not sure, if the lowmem-situation is relevant. on a newly booted machine there are no problems. The logs you include are odd.

[Dnsmasq-discuss] problem with not executed /etc/dhcp-script.d/10dhcpscript

(only CC'ing to openwrt-dev) under unclear circumstances, dnsmasq does not execute anymore the dhcp-script. the box in question had a short lowmem-situation, but dnsmasq itself was not effected (but crond/netifd). dhcp-actions are working normally. i have debug-output in the first line of the