[7912] in Release_7.7_team
Re: linerva / athena.dialup transition
daemon@ATHENA.MIT.EDU (Alex T Prengel)
Thu May 2 15:57:34 2013
From: Alex T Prengel <alexp@MIT.EDU>
To: Jonathon Weiss <jweiss@MIT.EDU>
Cc: linerva-root@MIT.EDU, release-team@MIT.EDU, alexp@MIT.EDU
In-Reply-To: <201305021558.r42FwOUp011522@outgoing.mit.edu>
Content-Type: text/plain; charset="ISO8859-1"
Date: Thu, 02 May 2013 15:57:23 -0400
Message-ID: <1367524643.7051.9.camel@dit>
Mime-Version: 1.0
Content-Transfer-Encoding: 7bit
I ran into a situation last week where a Third Party application
(CHEMKIN-PRO) wouldn't run on the dialups but did run on linerva, due to
not enough memory being available to the application (it's a Java app).
To reproduce:
add chemkinpro; chemkinpro
I told a student she could try running it on linerva (which I presume
she did as I didn't hear back). This is in current course use so
shutting linerva off before the semester ends could be problematic. It
would help if this could run on the dialups.
Alex
On Thu, 2013-05-02 at 11:58 -0400, Jonathon Weiss wrote:
> Hello,
>
> It's been a little while since we've talked about transitioning linerva
> users to athena.dialup.mit.edu. As you know the athena dialups were
> upgraded to Precise in February. In the process, I believe we added
> most of the features that had previously made linerva preferable to the
> dialups for some users.
>
> While we're unlikely to make changes to athena.dialup.mit.edu between now
> and the end of finals, I wanted to get an updated list of what things
> are currently blocking or interfering with the transition, so that we
> can work on eliminating them.
>
> Thanks
> Jonathon
>
> Jonathon Weiss <jweiss@mit.edu>
> MIT/IS&T/OIS Server Operations
