HP3000-L Archives

June 1997, 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:
Lee Gunter <[log in to unmask]>
Reply To:
Date:
Mon, 9 Jun 1997 09:04:45 -0700
Content-Type:
text/plain
Parts/Attachments:
text/plain (29 lines)
True ... however, if you use Image logging, an UPDATE CONFIG will
restore the state of the logging identifier table (DSTLGTAB) at the
time the CSLT was created, which will cause problems when the user
logging processes are restarted (current logfile numbers are not
correct).

Strictly speaking, is an UPDATE CONFIG required in this case?  Wouldn't
an UPDATE NOCONFIG restore the system files to the correct location?

Lee Gunter          [log in to unmask]
Regence HMO Oregon


______________________________ Reply Separator _________________________________
Subject: Re: [HP3000-L] disc space on drive 1
Author:  Gilles Schipper <[log in to unmask]> at ~INTERNET
Date:    6/8/97 12:37 AM


Re-reading what I wrote, I realize I may have been a bit nonchalant about
the potential problem asscociated with moving certain files off ldev 1.

You can indeed run into problems if some files from the SYS account do
stray off ldev 1 - even with a standard "START" from disk reboot.

However, you can always correct such problems prior to any reboot by simply
performing an UPDATE CONFIG from a current SLT tape.
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^

ATOM RSS1 RSS2