bind9 systemd related problems

Yuriy M. Kaminskiy yumkam+debian at gmail.com
Mon Feb 29 23:49:42 GMT 2016


Tollef Fog Heen <tfheen at err.no> writes:

> ]] Nikolay Shaplov 
>
>> Cause this bug affects a lot of cases and there is no way to solve it without 
>> touching /lib/systemd/system/bind9.service and it is not nice way at all...
>
> Read up on systemd snippets.
>
> You can just do:
>
> mkdir /etc/systemd/system/bind9.service.d
> echo "ExecStart=/usr/sbin/named -4 -f -u bind" > /etc/systemd/system/bind9.service.d/local.conf

You forgot "[Service]\nExecStart=\n" (extra "ExecStart=" is required to clear
existing value; otherwise it is interpreted as "two ExecStart", which is
forbidden for anything but Type=oneshot)

> and it'll start with -4.

Then package maintainer adds/change some option/path, and you'll miss that on
package upgrade because nothing can notice and warn you.





More information about the Pkg-systemd-maintainers mailing list