-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Whenever the config is updated via DBus, the complete set of upstream servers is logged, I think. Cheers, Simon. On 22/06/15 14:34, CircleCode wrote: Hi, with dbus interface enabled, the config dnsmasq runs with is something like dynamic.
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 If you have the latest release, 2.73 then - --log-queries=extra Will enchance the logging format in a way which makes it easier to link requests and replies. Cheers, Simon. On 28/06/15 12:54, ma...@manfbraun.de wrote: Hello ! I am just
I have fixed the problem by including Requires=systemd-resolved.service After=systemd-resolved.service in the systemd service file for dnsmasq and it now boots correctly. On 5 July 2015 at 21:17, R bjorkeg...@gmail.com wrote: dnsmasq segfaults at boot and systemd fails to load the service. (
dnsmasq segfaults at boot and systemd fails to load the service. ( http://sysv.se/journal.txt ) after the boot process systemd can start dnsmasq successfully through 'systemctl start dnsmasq' and everything works. This started happening after I switched from using netctl + dhcpcd to configure my
Is this a bad question? Am 21.06.2015 um 21:13 schrieb Anton Blau: Hello, please excuse my bad englisch. I am not a native speaker. I run dnsmasq with openvpn on my Debian Router. After the upgrade to jessie dnsmasq crashes on the boot because the openvpn device isn´t up. openvpn starts as
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Using monotonic time seems to be a bit of a portability nightmare, as an alternative, I've added code to count the number of zero returns from select(). The standard wait is three seconds, so once select() has returned zero 12 times, the loop ends
Hi Anton, it might have helped if the error messages weren't in German... ;-) Debian Jessie is using systemd as init system. systemd does not always start legacy services (those described in /etc/init.d rather than /etc/init) in the order you would expect (for more details, see