On 16/06/15 18:34, Arnt Gulbrandsen wrote:
Anto writes:
So I am not really sure what you meant by "reading the new directives
at boot time". Which directive would that be, where is it located and
which package provides that?
You read things like
# Provides
and
# Required-Start
to generate an Epoch configuration in /etc/epoch.conf (or some other
filename). Epoch then reads that file to generate an Epoch
configuration in RAM.
What I am saying is: Why bother with generating the configuration
file? Why not just generate the in-RAM configuration? That is, why not
teach Epoch a new configuration option, documented as following: "When
you enable this option, Epoch reads the LSB-Start-Before and ...
options in /etc/init.d/*, and starts servers accordingly. Note that
Epoch does not run /etc/init.d/*, it merely reads the LSB-Start-Before
and ..."
This is tricky. It's quite possible that doing this directly is a bad
idea, and that it actually is better to use the detour via the config
file.
Arnt
Hello Arnt,
Thanks a lot for explaining your point in more detail.
If I correctly understood, that means the function which you suggested
must be implemented inside epoch rather than being implemented
independently outside epoch and any other packages which generate
sysvinit files on /etc/init.d. That would be a great feature for epoch
if epoch maintainer agreed to implemented it the way we thought it
should be. If epoch maintainer disagreed or implemented that differently
then we are back to square one. I prefer to avoid this situation and not
to touch both the upstream epoch and all packages which daemons need to
be managed by epoch.
Cheers,
Anto
_______________________________________________
Dng mailing list
Dng@lists.dyne.org
https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
