Re: insserv + apache2 + bind9 = pain
On Thu, Dec 30, 2010 at 3:50 PM, Mike Bird <mgb-debian@yosemite.net> wrote:
> On Thu December 30 2010 12:13:03 Tom H wrote:
>> On Thu, Dec 30, 2010 at 1:57 PM, Mike Bird <mgb-debian@yosemite.net> wrote:
>>>
>>> Your solution is to edit /etc/init.d/apache2. Your solution requires
>>> manual intervention on every apache2 upgrade.
>>
>> Apparently not:
>> http://lists.debian.org/debian-user/2010/12/msg00550.html
>
> I see. So for packages which "respect editing /etc/init.d/"
> files, manual intervention is required every time the
> packager changes the virgin "/etc/init.d/" file, but not
> necessarily on every upgrade.
>
> Thank you, Tom.
>
> Nevertheless, this is still more manual intervention than
> if the override is placed in /etc/insserv/overrides, or some
> but not all of the many other places where dependencies can
> be declared.
>
> Some of the open questions are which of those many places are
> reserved for Debian packagers and which are reserved for
> sysadmins; and which if any will be automatically converted
> to systemd or launchd or upstart when insserv is thrown out.
You're welcome.
IIUC, you'll be prompted at every upgrade of "/etc/init.d/apache2" to
choose between your local copy or the maintainer's or to view a diff
(or a fourth option that I can't remember at the moment; shell
prompt?).
As a sysadmin, I'd choose to use "/etc/insserv/overrides" or
"/etc/insserv.conf.d" rather than "/etc/init.d" or "/etc/insserv.conf"
respectively if at all possible.
As an aside, you refer to the pre-insserv setup as "Snn/Knn startup
mechanism" but insserv doesn't deviate from that style. insserv
creates the Snn/Knn symlinks dynamically in an order determined by a
set of dependencies. pre-insserv the symlinks' order was set
statically by the maintainers.
No comment on the post-insserv setup except to say that I hope that it
isn't launchd because I'd rather not have to deal with its xml daemon
and agent definitions.
Reply to: