On 08/06/12 14:47, Ritesh Raj Sarraf wrote: > On Friday 08 June 2012 01:05 PM, Tollef Fog Heen wrote: >> ]] Ritesh Raj Sarraf >> >>> Do you want this bug re-assigned to dnsmasq? I think it fits in on >>> systemd. systemd should be a drop-in replacement. But then, systemd >>> doesn't claim to be a drop-in replacement. It states that applications >>> need to be modified (systemd-ized) and adapt to systemd. >> Given dnsmasq ships a .service file, it's dnsmasq's responsibility to >> ensure it has the same behaviour with both service definitions. So, >> this bugs belongs in dnsmasq. >> > Tollef: The bug has a good amount of detail. I think there are use cases > that systemd does not cover. In this case, it is reading the variables > from the /etc/default/dnsmasq file. The bug has the details. Please > correct if things have changed otherwise. > >
The real problem here is not /etc/default/dnsmasq, it's the code in /etc/init.d/dnsmasq which links dnsmasq and resolvconf. What is required is: 1) Pass an extra command-line argument to dnsmasq iff /sbin/resolvconf exists. 2) Run "echo "nameserver 127.0.0.1" | /sbin/resolvconf -a lo.dnsmasq" after dnsmasq has started succesfully (ExecStartPost should do that) but again, only if /sbin/resolvconf exists. 3) run "/sbin/resolvconf -d lo.dnsmasq" after dnsmasq has stopped. (ExecStopPost) The difficult part of this seems to be that different actions are needed depending of if resolvconf is installed or not. Simon. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
