[25675] in Hotline Meeting
RE:WHOI problem
daemon@ATHENA.MIT.EDU (jjmorey@MIT.EDU)
Wed Nov 23 07:29:21 1994
From: jjmorey@MIT.EDU
To: hotline@MIT.EDU
Date: Wed, 23 Nov 1994 07:29:16 EST
------- Forwarded Message
Received: from MIT.MIT.EDU by po8.MIT.EDU (5.61/4.7) id AA22277; Tue, 22 Nov 94 18:03:26 EST
Received: from BIGREDONE.MIT.EDU by MIT.EDU with SMTP
id AA20672; Tue, 22 Nov 94 18:03:13 EST
Message-Id: <9411222303.AA20672@MIT.EDU>
Date: Tue, 22 Nov 94 18:03:29
From: burke@MIT.EDU (Jerry Burke)
To: eric@pearl.whoi.edu
Subject: hardware problem - is a system patch
Cc: ops@MIT.EDU, nschmidt@MIT.EDU, dcns-cluster@MIT.EDU
HI Eric,
The move of a machine in WHOI is not a trivial matter for us. We have to
be notified in advance about new subnets, becuase the rc.net file
contains the information for the current WHOI subnet we agreed to have
in our rc.net file.
Now, since you moved to a new subnet it is not in our rc.net file and
it takes time to put the patch in the release. The ops group is aware of
your problem and are talking to release engineering staff and are trying
to make a new release to allow for your move. This is scheduled for
January 31st.
Your option for now is to move the workstation back, or maintain your
own rc.net file.
In the future it is best for you to notify hotline in advance of your
moveing workstations to different subnets. That way we could plan for
these patches to the releases.
Thanks, Jerry
It sounds like Eric moved a workstation, which he probably shouldn't
have. But then (at least as he tells it) he was given a run-around
between hotline,system support, and network folks. How should we have
handled this so that he didn't go to OLC as a last resort? Or did he
just misunderstand what we were telling him?
Naomi
- ------- Forwarded Message
Received: from MIT.MIT.EDU by po6.MIT.EDU (5.61/4.7) id AA05382; Tue, 22
Nov 94 11:07:51 EST
Received: from PEARL.WHOI.EDU by MIT.EDU with SMTP
id AA00386; Tue, 22 Nov 94 11:07:39 EST
Received: by pearl.whoi.edu.whoi.edu (4.1/SMI-4.1)
id AA09839; Tue, 22 Nov 94 11:07:35 EST
Date: Tue, 22 Nov 94 11:07:35 EST
From: eric@pearl.whoi.edu.whoi.edu (Eric Cunningham)
Message-Id: <9411221607.AA09839@pearl.whoi.edu.whoi.edu>
To: jjmorey@MIT.EDU
Subject: Re: Hardware Problem?
Cc: hotline@MIT.EDU, nschmidt@MIT.EDU, ecunningham@whoi.edu
> I was notified by OLC that someone from WHOI had called them
> about a system that was moved and that the system was having
> problems coming back up. From the description it sounds like
> the same problem you where having with menhaden in Oct. Are
> you aware of this situation? And any problems with the Hardware
> or software at WHOI in the future, need to be called into the
> Athena hardware hotline 253-1410 not OLC.
This is the same problem that first I reported in October re:
menhaden. The system is up now, but because I need to include
new gateway info in menhaden's local rc.net, I still have the
problem that any software downloads/upgrades wipe my local changes
and require that I re-edit my local file. Since this is a
maintenance headache that can be avoided (simply, I thought) I'm
still trying to get the correct gateway info in place at MIT so
software downloads will include the info needed by menhaden to
boot automatically w/out my having to edit anything (like it used
to be before menhaden was moved).
The only reason OLC was dragged into this was because I couldn't
get anywhere w/hotline since it is net folks' problem and they
offer no solution for this since it is felt to be system support
folks' problem; system support folk say to wait for a future
software release. Someone along the line suggested I use OLC for
this. So, I think I've involved just about everyone there is at
this point!
- ------- End of Forwarded Message
------- End of Forwarded Message
