|
From: Dick M. <di...@fo...> - 2010-05-11 15:35:41
|
On 05/11/10 15:27, roy barnard wrote: > If I just add the commands I need to the specific init.d scripts, then it will solve my issues but it also means I will need to edit and maintain these scripts each time I upgrade to the next version of DL. If I need to apply patches to any of my modified init.d scripts (from mantis for example), I will need to remove my changes, patch and then reapply my changes. > > I was trying to think about more of a global solution. If this is an issue for me then I always try to consider if it might be an issue for others. ... > Does anyone else need this type of configuration flexibility? It seems like a lot of overhead to run maybe one script. It does depend how much this capability is likely to be used. Although a bit of a bodge I think it would be more appropriate for one to patch the few init files that are affected after each reinstall (a relatively rare event) than impose all this dynamic on every service just in case. Or better still put the service in a wrapper script so that all startup matters are part of the application concerned. Dick |