On 3-16-13 23:52:39 Reindl Harald wrote: > Am 16.03.2013 23:37, schrieb Garry T. Williams: > > It seems that NM kills the running dnsmasq and then restarts it. > > The new instance sometimes fails to bind because the old instance > > hasn't finished closing the port. > > > > My work-around is to: > > > > sudo systemctl start dnsmasq.service > > > > when I notice the failure. How can I eliminate this race? > > systemd supports auto-restart of services and nobody knows why it is > not used as default while i have it for ANY service since Fedora 15 > in production use > > yes, it's a workaround but it should work without user interaction > and since i avoid NetworkManager and use the classical > "network.service" with a static config nor have installed NM on > anymachine............. Yes. This is a better work-around. Thanks for the suggestion. -- Garry T. Williams -- users mailing list users@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines Have a question? Ask away: http://ask.fedoraproject.org
