В письме от 1 марта 2016 02:49:42 пользователь Yuriy M. Kaminskiy написал: > Tollef Fog Heen <[email protected]> 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)
Thanks! That worked for me! > > 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. Yeah! I hope bind9 maintainers will fix init system independent way to add additional options for starting bind9 _______________________________________________ Pkg-systemd-maintainers mailing list [email protected] http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-systemd-maintainers
