[26116] in Athena Bugs
Re: linux 9.3.11: matlab
daemon@ATHENA.MIT.EDU (Alex T Prengel)
Wed Oct 13 18:24:48 2004
Message-Id: <200410132223.i9DMN9JW013216@dit.mit.edu>
To: Camilla R Fox <cfox@mit.edu>
In-reply-to: "[26112] in Athena Bugs"
In-Reply-To: Your message of "Wed, 13 Oct 2004 17:07:14 EDT."
<200410132107.i9DL7EqJ012163@red-herring.mit.edu>
Date: Wed, 13 Oct 2004 18:23:09 -0400
From: Alex T Prengel <alexp@mit.edu>
cc: bugs@mit.edu
cc: alexp@mit.edu
Errors-To: bugs-bounces@mit.edu
>I moved my afs homedir to a fileserver in w92, just to be sure; I can
>still reproduce the problem reliably.
>
>Cleaning out my .sw_messages hasn't helped, either; if I move it aside,
>it gets created empty next time I run matlab.
So I need to be sure I understand what you're seeing- when you have no
~/.sw_messages file at all, and you run Matlab, it prints the "Matlab
7.0.1.." message, and if you then exit Matlab, you just see a 0
length .sw_messages file?
What I thought you were saying was that you have the line
matlab7.0.1_avail
in your ~/.sw_messages file, but were still getting the message
repeated, and possibly multiple copies of that line in ~/.sw_messages
on each subsequent launch... in that case my suggestion about timing
might have been relevant- otherwise probably not.
Here's what's supposed to happen (and does for me, every time):
I delete ~/.sw_messages.
I start Matlab, I get the message. When I exit, I see .sw_messages,
with a single line:
matlab7.0.1_avail
I restart Matlab as before; I don't get the message. File .sw_messages is
unchanged.
Are you sure the matlab you're running is
/mit/matlab/arch/$ATHENA_SYS/bin/matlab and not some other matlab? That might
explain it. Only the base locker matlab wrapper script does the messaging
correctly...
This may seem like an odd question- but are you sure you can create a non-zero
length file in your home directory? If not, that would explain what you're
seeing but I kind of doubt it. Can you try using another account? Do you
still see the problem?
If no clues emerge from the above, I'm stumped. You might ask Garry to read
this thread- he's the the closest to a maintainer for the cookie messaging
system that we have at the moment... he did make a modification to the message
sender recently to deal with a blocking issue, but I sort of doubt that it's
releated to your problem... and I don't see it.
Alex
