HP3000-L Archives

August 1998, Week 1

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:
Andreas Schmidt <[log in to unmask]>
Reply To:
Date:
Mon, 3 Aug 1998 10:56:43 +0200
Content-Type:
text/plain
Parts/Attachments:
text/plain (45 lines)
thanks for sharing this!

Best regards, Andreas Schmidt, CSC, Germany





[log in to unmask] on 07/31/98 09:45:26 PM

Please respond to [log in to unmask]

To:   [log in to unmask]
cc:    (bcc: Andreas Schmidt/HI/CSC)
Subject:  Re: system logging disabled




[log in to unmask] on 7/31/98 wrote:
> Yesterday we lost a mirrored disk, resulting in an I/O error loop which
> generated many, many LOG####.PUB.SYS logfiles until
> MPEXL_SYSTEM_VOLUME_SET ran out of disk space.
> I've purged most of the offending log files (the CE has been here and > left,
the drive is replaced) so there is now plenty of free disk space, > but system
logging remains disabled and is unwilling to resume:
  <snip>
> @221 System logging is not enabled at the present time.
> System Logging message 900
> From what I've read, a reboot should clear this, but I was wondering if
> there was anything else I should be trying that won't require a
> reboot.....
Mark,
The same thing happened to me on several occasions.  I was given the command
file below, STARTLOG.PRVXL.TELESUP, by the HPRC to resume system logging WITHOUT
a reboot.  It has worked fine for me!
debug var log_addr [a.c0000004+#248*8]; dv log_addr,64/4; &
mv log_addr+5c,,,$01000000; dv log_addr,64/4; e
SWITCHLOG
John Hornberger
Sr. Systems Programmer
General Signal Services
[log in to unmask]
P.S.  Insert standard disclaimers here!

ATOM RSS1 RSS2