> -----Original Message-----
> From: Robert G. Brown [SMTP:[EMAIL PROTECTED]]
<snip>
> (More than 2c worth, I know, but these are very strong opinions with
> many, many years of experience behind them. Drives me nuts when folks
> confuse religious issues like layout with functional issues like "can I
> manage it with a GUI". Heck, one could boot init from ONE SINGLE
> monolithic rc script with a command line argument for runlevel and it
> would work just fine and be probably even easier to either hand-edit or
> runlevel-manage with a GUI than any of the paradigms we have today.)
>
> Robert G. Brown http://www.phy.duke.edu/~rgb/
> Duke University Dept. of Physics, Box 90305
> Durham, N.C. 27708-0305
> Phone: 1-919-660-2567 Fax: 919-660-2525 email:[EMAIL PROTECTED]
----end
For my 2c's worth, I would suggest that the scripts log *all* the output; be
it status,
or error messages. Its fun trying to catch a message that lasts for less
than a second
on the screen, before it disappears <NOT>.
I have spent quite a bit of time, rewriting a lot of startup scripts, so
that the output
is logged. I know this adds to the 'ever increasing log file' problem. But
being able to
see the output of each script, for me, is much more important. (Because I am
the
one that gets to fix it).
I have thought that this is one area in *IX administration that could do
with a major
rethink. I would like to be able to make rules for startup files, instead of
'is the file
named S[0-9][0-9]*'. For instance, I would like to start apache IF, I had a
network card
that had been configured to work. I know I could, and I do, add these to
startup scripts,
but I keep having to do this.
When I manage a site, I try and keep all the startup files identical, on all
hosts (and
in a heterogeneous environment as well). This means that I don't have to
keep track
of all variations of every package that needs to be boot time started. It
also means
that I can switch servers very quickly (more important).
Any comments?
Simon
