Path: utzoo!utgpu!watmath!clyde!bellcore!rutgers!rochester!cornell!uw-beaver!rice!sun-spots-request
From: slevy@uf.msc.umn.edu (Stuart Levy)
Newsgroups: comp.sys.sun
Subject: Re: wierd uucico bug
Message-ID: <8811252000.AA04503@uf.msc.umn.edu>
Date: 10 Dec 88 06:17:19 GMT
Sender: usenet@rice.edu
Organization: Rice University, Houston, Texas
Lines: 12
Approved: Sun-Spots@rice.edu
Original-Date: Fri, 25 Nov 88 14:00:51 CST
X-Sun-Spots-Digest: Volume 7, Issue 42, message 5 of 13

We occasionally see something that might cause those symptoms.  Once in a
while, it seems as though the cached text for some binary will be
corrupted.  The *file* will appear fine, but everybody on the system will
find that that binary won't run, dumps core or whatever.

It can be "fixed" by renaming the real binary & copying the renamed binary
to its usual name.  Since the new binary is a different inode, those
cached pages don't apply to it.  After a while (when all the executing
copies exit?) the cached pages go away and the old binary will work too,
so you can rename it back.

	Stuart Levy