lfs-bootscripts 2.0.2 (long)

Nathan Coulson conathan at conet.dyndns.org
Thu Mar 25 21:12:32 PST 2004

> Dagmar d'Surreal wrote:
>> This stuff seems to severely reduce our functionality as well.  There
>> appears to be no way to disable a service without removing it's script
>> or link.  In the current method, a service can be entirely disabled by
>> chmodding it's script 000, in this method, if it makes that check, it's
>> not being mentioned in the documentation.
> In fact, I use this method (chmod -x unused.initscript) and was also going
> to ask whether it is the right way of doing things.

):  I never did look at the contrib stuff.  depends what test they use I

> And concerning the documentation: the existing documentation (i.e. README
> in
> the LFS/bootscripts directory in CVS) only documents existing
> configuration
> files. Functions in the "functions" fime are documented nowhere, so one
> effectively cannot write his own (additional) LFS-style initscripts based
> on the documented interface and not on the implementation read in the
> "functions" file. It's a bug:
> http://bugs.linuxfromscratch.org/show_bug.cgi?id=797
> --
> Alexander E. Patrakov
> --

sorry about the readme.  It only contains how to use the /etc/sysconfig
configuration scripts.  [as you already said].  Once I get some of my
homework out of the way, I'll see if I can expand the documentation

now if I can figure out how to confirm bugs...

for the record, the reason why killproc is unsuitable for mysql, is when
you dont use sysvinit's pidof program.  [it always sticks mysql's main
daemon at the front of the list (no clue why)].  [I guess some people
prefer to use psmisc's, or whatever it was called, which sorts it in
numerical order].

oh well, at least that can be cleard up in the future.  [going to see if
we can handle the PID files]

More information about the blfs-dev mailing list