29 Sep
2011
29 Sep
'11
11:33 a.m.
I want to make sure xend stops after corosync etc so that the cluster
can take care of migrating the domains off of the machine when it
reboots, but I don't want to modify the init.d files directly in case
they get overwritten on an upgrade.
Is there a place I can put this information to make sure the scripts get
processed in the right order without actually changing the scripts
themselves?
Thanks
James
29 Sep
29 Sep
11:49 a.m.
On Thu, 29 Sep 2011, James Harper wrote:
I want to make sure xend stops after corosync etc so
that the cluster
can take care of migrating the domains off of the machine when it
reboots, but I don't want to modify the init.d files directly in case
they get overwritten on an upgrade.
I like debian. It's a release critical bug to overwrite things in /etc/
without asking the admin for permission. And I wouldn't be surprised if
conffile handling in the dh_ helper scripts automates this so it can't
easily be screwed up by careless maintainers.
Enterprise frickin' software. fsck you, deadrat!
Is there a place I can put this information to make
sure the scripts get
processed in the right order without actually changing the scripts
themselves?
I doubt it. The standard place, probably defined by FHS, is in the init
file headers itself.
--
Tim Connors
12:11 p.m.
Tim Connors wrote:
I like debian. It's a release critical bug to
overwrite things in /etc/
without asking the admin for permission. And I wouldn't be surprised if
conffile handling in the dh_ helper scripts automates this so it can't
easily be screwed up by careless maintainers.
*cough* /etc/motd.tail *cough*
4195
days inactive
4195
days old
2 comments
3 participants
participants (3)
-
James Harper -
Tim Connors -
Trent W. Buck