HP3000-L Archives

August 1996, Week 4

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:
Lars Appel <[log in to unmask]>
Reply To:
Lars Appel <[log in to unmask]>
Date:
Fri, 23 Aug 1996 19:11:09 MESZ
Content-Type:
text/plain
Parts/Attachments:
text/plain (21 lines)
Regarding the recent "uptime" tool discussion...
 
SYSDIAG LOGTOOL can also be used to check for recent reboots.
 
Just check for the system startup events (I guess it was event
code 101 but use TYPES command to verify). I do not know by heart
what capabilities LOGTOOL needs but reading a file in PUB.SYS
should work without PM or alike...
 
If you need info on recent START as well as UPDATE and INSTALL
then you might use SYSINFO.PRVXL.TELESUP (beware of PM and never
attempt to use the MPE/V SYSINFO program (CM) on an MPE/iX box).
 
Notice that SYSDIAG LOGTOOL will only work if you keep the system
logfiles around long enough. (My daily "cleanup" job deletes LOG,
NMLG and spoolfiles that haven't been accessed for about a week).
 
Lars/iX
 
([log in to unmask] - but speaking for lappel here, not for hp.com)

ATOM RSS1 RSS2