HP3000-L Archives

January 1999, Week 3

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:
Neil Harvey <[log in to unmask]>
Reply To:
Neil Harvey <[log in to unmask]>
Date:
Tue, 19 Jan 1999 06:29:57 +0200
Content-Type:
text/plain
Parts/Attachments:
text/plain (74 lines)
Also, there is a little file that records the date and time of the last
boot, so:-

print logdcc.pub.sys > logtemp
input uptime < logtemp
echo This HP3000 was last booted on !uptime
purge logtemp,temp

will show this.

Neil

> -----Original Message-----
> From: Wirt Atmar [SMTP:[log in to unmask]]
> Sent: Tuesday, January 19, 1999 3:47 AM
> To:   [log in to unmask]
> Subject:      Re: last restart
>
> Stan writes:
>
> > Re:
> >
> >  > I know that there is a utility which will show at least the last
> system
> >  > restart, but at the end of this day, cannot remember what it is.
> Can
> > someone
> >  > remind me, please?
> >
> >  UPTIME, from: http://www.allegro.com/software/
> >
> >  Note: if you have a version older than 99A, then you'll want to get
> >  the newest version (99B).
>
> There is another way to get the same information. Run SYSINFO
> (generally found
> in the PRVXL group of the TELESUP account) and type the command MI
> (for
> miscellanceous information). You'll get a display that will be similar
> to
> this:
>
> ----------------- Miscellaneous System Information -----------------
>
>           -------------------Boot Info--------------------
>
> System booted from Config Group CONFIG
>
> Last Boot            SUN, DEC 27, 1998,  4:39 PM
> start norecovery
>
> Last Install         FRI, MAY 15, 1998,  6:58 PM
> install
>
> Last Update          TUE, SEP  1, 1998, 12:45 PM
> update
>
> Previous Start       SUN, NOV 15, 1998,  7:52 PM
> start norecovery
>
> Last Dump            (Not Recorded)
>
> As noted by others, SYSINFO is not 100% safe with disc mirroring in
> place, but
> even then, the MI command is not likely to cause any problems. It is
> not
> likely to be performing any of the low-level I/O commands that seem to
> cause
> the problems. But as the message at the beginning of SYSINFO says,
> "Youse uses
> this programs at youse own risk."
>
> Wirt Atmar

ATOM RSS1 RSS2