HP3000-L Archives

September 2001, Week 2

HP3000-L@RAVEN.UTC.EDU

Options: Use Monospaced Font
Show Text Part by Default
Show All Mail Headers

Message: [<< First] [< Prev] [Next >] [Last >>]
Topic: [<< First] [< Prev] [Next >] [Last >>]
Author: [<< First] [< Prev] [Next >] [Last >>]

Print Reply
Subject:
From:
Michael L Gueterman <[log in to unmask]>
Reply To:
Michael L Gueterman <[log in to unmask]>
Date:
Wed, 12 Sep 2001 07:17:25 -0500
Content-Type:
text/plain
Parts/Attachments:
text/plain (30 lines)
Gary wrote:

<snip>
>
>#3, I have to disagree.  I think that it would be greatly beneficial if the
>command would be able to preprocess some type of shutdown file.  Much like
>SYSSTART.  Perhaps SYSSTOP?

The problem I see with the command itself processing a script is that you
may want/need alternate scripts based upon the reason for the shutdown
as well as needing to build in a mechanism to decide whether the
preprocessed
functions worked as expected and THEN decide whether or not to continue
with the actual shutdown.  If all of that preprocessing logic were in
separate command files, you can "roll your own" based on the situation.
I don't want to be tied into a single "shutdown script" as it were.
Of course, if it were an optional file, then I could just opt not to use
it and still get what I need :)

Regards,
Michael L Gueterman
Easy Does It Technologies LLC
http://www.editcorp.com
voice: 888.858.EDIT or 573.368.5478
fax:   573.368.5479
--

* To join/leave the list, search archives, change list settings, *
* etc., please visit http://raven.utc.edu/archives/hp3000-l.html *

ATOM RSS1 RSS2