On Fri, 2011-09-02 at 16:04 +0100, Simon Kelley wrote: > Michael Stapelberg wrote: > > Hi Sjoerd, > > > >> When using systemd starting dnsmasq just hangs and times out.. Also the > >> sysv > >> init script seems to have a reasonable amount of functionality that the > >> systemd > >> one does not have, so i'm not sure if switching now is the right thing.. > > Which version of systemd do you use? I tested the service file with systemd > > 29
Latest in debian, so 29 > > and it works just fine: > > > > michael ~ $ sudo systemctl start dnsmasq.service > > michael ~ $ systemctl status dnsmasq.service > > dnsmasq.service - A lightweight DHCP and caching DNS server > > Loaded: loaded (/lib/systemd/system/dnsmasq.service) > > Active: active (running) since Fri, 02 Sep 2011 16:25:45 +0200; 700ms > > ago > > Process: 28971 ExecStartPre=/usr/sbin/dnsmasq --test (code=exited, > > status=0/SUCCESS) > > Main PID: 28973 (dnsmasq) > > CGroup: name=systemd:/system/dnsmasq.service > > └ 28973 /usr/sbin/dnsmasq -k > > > > Can you please do the following? > > > > 1) Run strace -o /tmp/strace.log -fF -tt -s2048 -p 1 > > 2) Run systemctl start dnsmasq.service > > 3) Attach the (bzip2'ed) contents of /tmp/strace.log Sure attached. Looks like you're using a dbus service, while by default (afaik) dnsmasq isn't configured to connect to dbus, so it'll just wait forever and ever.. > > > > • The resolvconf stuff I regard as obsolete when using NetworkManager or > > some > > other configuration tool. > > Hmm, I'm not going to argue that one ;-) As long as you ensure NM still correctly interacts with dnsmasq such that all local nameserver queries can go via dnsmasq and dnsmasq uses the resolv.conf file written by NM this might be true. There are other cases where resolvconf is useful though (essential every time you get dns servers from multiple services).. I'm not sure that just taking the stanza that resolvconf is useless is a useful one at this point... -- Sjoerd Simons <[email protected]>
strace.log.bz2
Description: application/bzip
