On Wed, Jun 05, 2002 at 04:37:28PM -0400, Mike Dresser wrote:
> how about an exit 0, in the top of /etc/init.d/inetd after shutting it
> off?
This will work, but it can cause confusion in the future, especially if
somebody else takes over as admin on the box. They'll see inetd
configured to start in the rc symlinks, but they won't know why the init
script doesn't do anything unless they go and look at it directly. Not
a hard problem to troubleshoot, but why be nonstandard unless you have
to?
IMHO, the Right Way(tm) to manage init scripts on a SysV-style system is
by using the SysV symlink structure. It's what people expect, it's
straightforward, and you don't have to rewrite any system-level scripts
which could change with future upgrades.
-mrj
--
# Michael Jinks, IB # JFI/MRSEC/EFI Computing # University of Chicago #
Reader! Think not that
technical information
ought not be called speech; -- Anonymous, "How to decrypt a DVD"
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
