|
From: roy b. <roy...@ya...> - 2010-05-16 15:12:38
|
All,
Thanks for taking time to discuss this idea.
Following up on replies in no specific order.
>>Heiko:
>>Although I like the idea, I'm still not convinced that we should do it.
>>It may be something we should add to Mantis for 1.5
>>(I created that project already in Mantis).
>>I'd rather get a final 1.4 out, so we can start working on new features but still have a stable tree.
Please don't delay 1.4 for this.
When we have a general agreement I will back port to my 1.4 Version knowing that the functionality will be in later versions.
>>Heiko:
>>would it help to have multiple boot.xxx scripts?
>>E.g. boot.mountfs, boot.network, boot.last ?
>>We would consider those user-scripts, just like the boot.local one.
I don't know. Depends when the scripts are run and what is ready/not ready in the ram drive.
>>Serge:
>>In general, I like the idea, because it shows the unified way for init script extensions.
>>And, the most attractive part, it's disabled by default :)
I always try to ensure my idea's don't change the underlying functionality.
I break less this way.
>>Heiko:
>>*If* we would implement something like the proposal below,
>>I'd rather call 1 script and just give it a parameter like 'prestart' or 'poststop'.
>>This way there would be a lot less scripts.
I don't like the one script idea as it immediately cut down the functionality, unless the same script is called at lots of different places but that just makes things more complicated.
New Idea:
I have given this more thought and I have a modified version of my suggestion, that might be a better compromise but still giving the functionality that I would like to see.
In Centos the starting and stopping of services is handled by a script called "service". Eg: service squid stop
If this script was created which handled my pre-start/pre-stop/post-start/post-stop system as described before, then the only change to DL would be to patch the /etc/init.d/rc script to use the new "service" script only if required.
Reasons:
uses Dick's suggested a wrapper script idea.
no changes to the existing init.d scripts.
Give me the required functionality.
Disabled by default as Serge likes.
Only requires modifying one existing script (/etc/init.d/rc)
/etc/init.d/squid stop works as expected.
easily ports backwards/forwards.
But......
/etc/init.d/service squid stop
would run any required pre-stop scripts call "/etc/init.d/squid stop" and then run and post-stop scripts.
I would make "service" to the /etc/init.d/ script even if there are no additional scripts.
I will mock this up over the next few days an report back.
Please feel free to comment on this new idea.
Many Thanks,
Roy Barnard
|