27;
'
LINENO=''
OPTIND='1'
PATH='/usr/sbin:/usr/bin:/sbin:/bin'
PPID='19337'
PS1='\w \$ '
PS2='> '
PS4='+ '
PWD='/'
SHLVL='1'
TERM='linux'
USER_DHCPSCRIPT='/etc/dhcp-script.d/10dhcpscr
* Simon Kelley [12.05.2017 08:33]:
> Oops. "It compiles - ship it" bites back.
>
> 2.77rc3 fixes this, and we're currently eating the dog-food chez Kelley.
just to mention it, the loopback-thingy is working fine now on my side with rc3.
Thanks a lot!
bye, bastian
__
* 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-dhcp[28815]: DHCPREQUEST(lo)
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
# k
* Nicolas Cavallari [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 checked my scripts again and again - i have t
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 filen
* Simon Kelley [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. Doing DHCP on the loop
(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 scri
