Re: [Devil-linux-develop] Setting up directories in /var during boot.

[Serge L. <fi...@in...>]

Heiko,

I'd understood it a bit different way.

Each init script has 4 external calls (pre/post start, per/post stop) and those
scripts are in the following filesystem hierarchy

	xxxx/start/pre/<service-name>
	xxxx/start/post/<service-name>
	xxxx/stop/pre/<service-name>
	xxxx/stop/post/<service-name>

Those calls might be commented out by default to decrease unnecessary activity.

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 :)


Serge

On 05/14/2010 10:25 AM, Heiko Zuerker wrote:
> Hey,
> 
> 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.
> 
> Heiko
> 
> Quoting roy barnard <roy...@ya...>:
> 
>> Dick,
>>
>>> 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
>>
>> I don't disagree.  On my main firewall I run the same version of DL  
>> for a year or two then upgrade.
>> When a new major version comes out I normally follow the Release  
>> Candidates, so this would incease my testing.
>>
>> I agree that the idea of only patching init.d scripts as required is  
>> "a bit of a bodge" and in my opinion makes things more difficult for  
>> others using the mechanic,as they would first have to check if the  
>> required init.d has been patched for Pre-Start scripts and then  
>> created the directory as per previous email.  I think this make the  
>> idea more complicated, I don't now if that is an issue as I would  
>> expect DL to be used by Linux Savvy SysAdmins.
>>
>> I did consider using an eviroment variable to enable/disable the  
>> functionality but as the directory existance checks are on the ram  
>> drive I could see no gain.
>>
>> I am interested in your other comment:
>>> Or better still put the service in a wrapper script so that all
>>> startup matters are part of the application concerned.
>>
>> Can you please expand your wrapper script idea, as this may be a  
>> better solution.
>>
>> Many Thanks,
>> Roy Barnard
>>
>>
>> --- On Tue, 11/5/10, Dick Middleton <di...@fo...> wrote:
>>
>>> From: Dick Middleton <di...@fo...>
>>> Subject: Re: [Devil-linux-develop] Setting up directories in /var  
>>> during boot.
>>> To: dev...@li...
>>> Date: Tuesday, 11 May, 2010, 16:20
>>> 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
>>>
>>>
>>>
>>> ------------------------------------------------------------------------------
>>>
>>> _______________________________________________
>>> Devil-linux-develop mailing list
>>> Dev...@li...
>>> https://lists.sourceforge.net/lists/listinfo/devil-linux-develop
>>>
>>
>>
>>
>>
>>
>> ------------------------------------------------------------------------------
>>
>> _______________________________________________
>> Devil-linux-develop mailing list
>> Dev...@li...
>> https://lists.sourceforge.net/lists/listinfo/devil-linux-develop
>>
> 
> 
>