<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0//EN" "http://www.w3.org/TR/REC-html40/strict.dtd"><html><head><meta name="qrichtext" content="1" /><style type="text/css">p, li { white-space: pre-wrap; }</style></head><body style=" font-family:'DejaVu Sans Mono'; font-size:9pt; font-weight:400; font-style:normal;">On Saturday 18 April 2009 04:56:22 Petter Reinholdtsen wrote:<br />> [Henrique de Moraes Holschuh]<br />> > The local modifications have to be done on the initscript headers, which are<br />> > conffiles since the dawn of time.<br />> <br />> This is not quite true. One can override a scripts headers by adding<br />> a file in /etc/insserv/overrides/, and that is how I propose to do<br />> local modifications.<br />> <br />> > There is also an override directory that can be used to change the<br />> > dependency headers instead of editing the initscript, but we should<br />> > get rid of any need to ship files in there as part of the release<br />> > goal (local admin can place stuff there as he wishes).<br />> <br />> There is actually two override directories,<br />> /usr/share/insserv/overrides/ and /etc/insserv/overrides/.<br /><br />These behave differently too; lsb headers in /usr/share/insserv/overrides/<br />only have effect for corresponding scripts in /etc/init.d/ that lack lsb info<br />alltogether. lsb headers in /etc/insserv/overrides/ trump all.<br /><br>
> <br />> Note that changes done to the list of enabled runlevels for a given<br />> service is preserved by insserv, while the sequence numbers are<br />> recalculated when the boot sequence is regenerated (typically when<br />> update-rc.d is executed).<br />> <br />> Happy hacking,<br /><br>
Thanks, Kel.</p></body></html>