HP3000-L Archives

August 2001, Week 5

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:
Reply To:
Date:
Thu, 30 Aug 2001 12:55:21 -0400
Content-Type:
text/plain
Parts/Attachments:
text/plain (25 lines)
X-no-Archive:yes
So I will ask a question that I have not asked for some time. When do I NEED
to make an SLT? In other words, what is on an exhaustive list of events on
an e3000 that will meaningfully change the contents of an SLT?

My own thinking is that one would want to make an SLT immediately after any
such event. One may or may not want to make additional SLTs at some regular
interval. But failing to make an SLT after making a change increases the
risk of having to use an old SLT without that change, even if that risk is
to miniscule as to be practically impossible.

The admins with whom I was having this disagreement thought is was
sufficient to make SLTs after weekly full backups, with no regard to whether
or not something had been changed in the last week. What struck me as odd
was that these admins worked Monday thru Friday, and so that was when these
changes were most likely to be made. Whereas, the full backups ran from
Saturday night thru Sunday morning. So SLT generation was on the back half
of the most distant time from when a change may have been made.

Greg Stigers
http://www.cgiusa.com

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

ATOM RSS1 RSS2