Sounds like it got low on disc space instead of general failure.  It
will happily twiddle its thumbs and not let you do anything while
waiting for some space to work with.

After it comes up you may want to do a general purge some of the
logfiles:

PURGE LOG####.PUB.SYS
PURGE NMLG####.PUB.SYS

Also abort any jobs that you see running, they may have been set to be
auto streamed after a reboot and could be eating up space.


Then you may have at least some disc space to start looking around for
OTHER items to eliminate.


Tracy Johnson
Measurement Specialties, Inc. 

BT







NNNN


> -----Original Message-----
> From: HP-3000 Systems Discussion 
> [mailto:[log in to unmask]] On Behalf Of Peter Smithson
> Sent: Friday, July 15, 2005 9:04 AM
> To: [log in to unmask]
> Subject: Re: [HP3000-L] Can't telnet to our hp3000
> 
> 
> I've found out a bit more.
> 
> If you re-boot it and then go to the pub for a chilli bowl 
> and a pint of real ale, come back and try to enter anything 
> at the console, it's managed to fall over all on it's own.  
> The last of the boot messages are there but you can't enter 
> any commands.  So I think it just falls over after a certain 
> time period.  You can run a few commands before it stops responding.
> 
> I have tried powering it down on one of the re-boots I did 
> yesterday but that didn't help.
> 
> It's not a good sign is it?
> 
> * To join/leave the list, search archives, change list settings, *
> * etc., please visit http://raven.utc.edu/archives/hp3000-l.html *
> 

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