http://bugzilla.suse.com/show_bug.cgi?id=1131075 http://bugzilla.suse.com/show_bug.cgi?id=1131075#c5 --- Comment #5 from Reinhard Max <max@suse.com> --- Hmm - maybe it could also be fixed via service file dependencies. I see that dnsmasq.service orders itself after network.target and before nss-lookup.target. Is there anything else it could hook to that makes sure it doesn't get started until /etc/resolve.conf is actually there? -- You are receiving this mail because: You are on the CC list for the bug.