sysV script execution logic/naming convention?

This is a multi-part message in MIME format...

------------=_1770824837-11351-6325
Content-Language: en-GB
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: quoted-printable

Hello dear list,

I have a question about execution of start/stop scripts.

For testing I created /etc/rc.d/init.d/test-a-script.sh (note hyphens,=20
dot and extension) with mode 755.
It simply contains the usual boilerplate and *before the case switch*=20
"echo ${0} ${*}; sleep 3".
I have then linked the script to rc.3/S90test-a-script.sh, and to=20
rc[036].d/K50test-a-script.sh.
It works when I call it manually, it works when the system boots, but I=20
don't see the message at shutdown.
Is there some kind of naming convention for the symlinks which I violate=20
using hyphens, dots and/or extension?
It seems unlikely since the start script gets executed but not the stop=20
script with the same naming convention.

The actual script I intend to install shall only run on shutdown, which=20
it doesn't, so I experimented with that testscript to find out about the=20
conditions for startup and stop.

What am I doing wrong?

Thanks +
stay healthy,
Thomas
--=20
"Do you wanna be a legend or a passing footprint on the sands of time?"


------------=_1770824837-11351-6325
Content-Type: text/plain; charset="UTF-8"
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
MIME-Version: 1.0

-- 
http://lists.linuxfromscratch.org/sympa/info/lfs-support
Unsubscribe: See the above information page
------------=_1770824837-11351-6325--