[26028] in Athena Bugs
Re: acrobat update notification
daemon@ATHENA.MIT.EDU (Alex T Prengel)
Wed Sep 1 00:48:14 2004
Message-Id: <200409010447.i814lwX4004824@astrophel.mit.edu>
To: Angie Kelic <sly@mit.edu>
In-reply-to: "[26020] in Athena Bugs"
In-Reply-To: Your message of "Tue, 31 Aug 2004 21:02:17 EDT."
<Pine.LNX.4.58L.0408312059270.5189@nighthawk.mit.edu>
Date: Wed, 01 Sep 2004 00:47:58 -0400
From: Alex T Prengel <alexp@mit.edu>
cc: alexp@mit.edu
cc: bugs@mit.edu
Errors-To: bugs-bounces@mit.edu
>Given that acrobat just added a fourth and fifth line to my
>.sw_messages I don't think the problem is gone.
Well, I'm at a loss. Neither Garry nor I can reproduce the
problem. I've tried many times, on both Linux and Sun... Garry points
out that the locker being replicated, the change in the
message-sending program wouldn't have propagated out of the R/W AFS
volume until after you began seeing the problem... it's pretty
unlikely that you were running it from the R/W volume...
I have one hypothesis that might explain what's happening. The message
sender first tries to read the .sw_messages file, looking for 5.0.9upgrade,
to decide if it should send the message again (and write 5.0.9upgrade to
the file). There could be a timing effect too. If your network is flaky
it might not be able to do the read in time (or at all maybe), thinks you
didn't get the message and sends it again (also writing to the file again).
Can you check out this possibility? It's all I can think of...
Alex
