HP3000-L Archives

September 2004, Week 5

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:
Gehan Gehale <[log in to unmask]>
Reply To:
Gehan Gehale <[log in to unmask]>
Date:
Wed, 29 Sep 2004 13:12:19 -0700
Content-Type:
text/plain
Parts/Attachments:
text/plain (36 lines)
In the 2 years since i've been working with the HP I've gotten used to
being ldev 4. I'm the first one in the office and the first to always
sign on and I never really though about it. I knew ldev 1, 2and  3
were taken by the system...
But today I come, log in and i'm ldev 5. I look to see who beat me to
work and it's a system proc...

:showdev
    1     DISC          N/A
    2     DISC          N/A
    3     DISC          N/A
    4   A UNAVAIL       SYS #87
    5   A UNAVAIL       #S88: 13 FILES

:showproc 87;system
QPRI  CPUTIME   STATE  JOBNUM  PIN  (PROGRAM) STEP

B149* 0:00.195  WAIT           87   (JSMAIN.PUB.SYS)

The other day HP came and swapped out a H.D. in our inclosure. I know
we rebooted the machine that day. Is there any reason this process
should still be running? Was it a hold over from the bootup that
should have logged off by now?
 Should I be worried or just leave it and get used to being ldev 5 from now on?


Not that the ldev really matters it was just a clue that something was
different..

Thanks,
Gehan Gehale
[log in to unmask]

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

ATOM RSS1 RSS2