Description of problem:
mt-st contains an init script for stinit. It's not an ordinary service, I realize that, but it should obey at least an applicable subset of guidelines for init scripts. Here are current problems:
1] When the 'service' isn't configured, ie. /etc/stinit.def doesn't exist, an attempt to start it prints nothing and exits with 0. It's supposed to exit with code 6.
On a related note, I see stinit it set to be started in all runlevels by default. So, *fortunately* it doesn't fail with an scary message by default, e.g. when system is booting, However, since it can't start unless it's configured, I suggest it be set not to be started by default at all. Users interested in this 'service' should configure it and mark it for starting in desired runlevels.
2] When the init script is executed with no or an unknown/unimplemented action, it correctly prints its usage message, but exits with 1. This should be 2.
Which implies that the 'stop' branch that does nothing should be removed, so that users trying to stop stinit get a usage message (and exit code 2). If you really want to special-case that, feel free to use exit code 3, but I think it's fine for 'stop' to fall into the category of invalid commands.
Version-Release number of selected component (if applicable):
See https://fedoraproject.org/wiki/Packaging/SysVInitScript for details.
Points 1 and 2 are fixed and LSB header is added. But I would like to keep the stop action as is, because exiting with an error could "break" the system shutdown.
Good point, thanks.
mt-st-1.1-4.fc12 has been submitted as an update for Fedora 12.
Thanks for updating the init scripts. It passes my test case now.
mt-st-1.1-4.fc12 has been pushed to the Fedora 12 stable repository. If problems still persist, please make note of it in this bug report.
*** Bug 786516 has been marked as a duplicate of this bug. ***