On Tue, Jun 16, 2015 at 05:34:49PM +0100, 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.
There are sometimes zombie files in /etc/init.d -- files that, by mishap or otherwise, didn't get deleted upon package deletion. Producing a config file gives the sysadmin a chance to edit it in case it's wrong. But fixing the files in /etc/init.d may be a better option. -- hendrik > > Arnt > > _______________________________________________ > Dng mailing list > Dng@lists.dyne.org > https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng _______________________________________________ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
