This is obviously a large amount of work, so thanks very much for that. To make use of it, I need to be able to see as clearly as possible what is being changed, and why. To that end, I'd much rather have diff files ten replacement files, but it's fairly easy to generate those for myself. Having
On 2018-12-02 01:01, M. Buecher wrote: I spent some time on how to keep backward compatibility for current configurations. The simplest solution would be to provide 2 systemd unit files: 1. An updated dnsmasq.service file for the main/default/standard "instance", that reflects the fix for
On 2018-12-01 16:19, Geert Stappers wrote: On Sat, Dec 01, 2018 at 01:20:58PM +0100, M. Buecher wrote: [Unit] Description=dnsmasq (%i) - A lightweight DHCP and caching DNS server Requires=network.target Wants=nss-lookup.target Before=nss-lookup.target The "Wants" and the "Before" have the
On Sat, Dec 01, 2018 at 01:20:58PM +0100, M. Buecher wrote: > [Unit] > Description=dnsmasq (%i) - A lightweight DHCP and caching DNS server > Requires=network.target > Wants=nss-lookup.target > Before=nss-lookup.target The "Wants" and the "Before" have the same targets. That feels odd to me.
Hello Simon, on my first tries to start multiple dnsmasq instances on Debian 9 "Stretch" with systemd I faced several issues and created Debian bug report #914305 . Yesterday I finally managed to spend several hours on the issue and found a clean solution for it. While preparing the text