[luv-main] stop/start info in /etc/init.d

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

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

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*
participants (3)
-
James Harper
-
Tim Connors
-
Trent W. Buck