HP3000-L Archives

August 1998, Week 2

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:
Joseph Rosenblatt <[log in to unmask]>
Reply To:
Joseph Rosenblatt <[log in to unmask]>
Date:
Thu, 13 Aug 1998 12:56:21 -0400
Content-Type:
text/plain
Parts/Attachments:
text/plain (18 lines)
I also have the situation where a console session can last all week.
This is not such a problem Sunday night through Saturday morning when we
have full coverage. From Saturday AM to Sunday PM there may be no
operator at the console.

The Computer Room, a misnomer as you will soon see, is electronically
locked. A log of who's "chip key" opened the door exists someplace deep
in the bowels of Building Services. The problem is that our "computer
room" is also our network server room, our PBX room and our Imaging
room. Too many people have access to our console (its the network guys
that scare me. Just enough knowledge to be dangerous and they don't
think crashing a server is such a big deal. After all Bill Gates taught
them to reboot for every problem.) The decision to limit the access is
not mine and there is nowhere else to put the other technologies.

Based on what everyone above me has said, I think I will have the
operator logoff on Saturday morning and logon Sunday night.

ATOM RSS1 RSS2