🚀 go-pugleaf

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