From owner-freebsd-questions  Sun Nov  2 23:24:47 1997
Return-Path: <owner-freebsd-questions>
Received: (from root@localhost)
          by hub.freebsd.org (8.8.7/8.8.7) id XAA13083
          for questions-outgoing; Sun, 2 Nov 1997 23:24:47 -0800 (PST)
          (envelope-from owner-freebsd-questions)
Received: from pegasus.com (pegasus.com [206.127.225.31])
          by hub.freebsd.org (8.8.7/8.8.7) with SMTP id XAA13062;
          Sun, 2 Nov 1997 23:24:38 -0800 (PST)
          (envelope-from richard@pegasus.com)
Received: by pegasus.com (8.6.8/PEGASUS-2.2)
	id VAA05159; Sun, 2 Nov 1997 21:24:08 -1000
Date: Sun, 2 Nov 1997 21:24:08 -1000
From: richard@pegasus.com (Richard Foulk)
Message-Id: <199711030724.VAA05159@pegasus.com>
In-Reply-To: Mike Smith <mike@smith.net.au>
       "Re: programs dying with SIGBUS after long uptime" (Nov  3, 11:15am)
X-Mailer: Mail User's Shell (7.2.5 10/14/92)
To: FreeBSD Questions <freebsd-questions@FreeBSD.ORG>,
        FreeBSD Hardware <freebsd-hardware@FreeBSD.ORG>
Subject: Re: programs dying with SIGBUS after long uptime
Sender: owner-freebsd-questions@FreeBSD.ORG
X-Loop: FreeBSD.org
Precedence: bulk

} 
} Note that once a text image has been corrupted during execution, 
} repeated execution of the same image will run the (corrupted) sticky 
} copy in core until same is flushed; this basically means that once a 
} program has died due to memory corruption you need to reboot.
} 

Or put a fresh copy of the binary into memory.  As an example, if
/bin/date is corrupted do this to refresh it:

	cp -p /bin/date /tmp
	mv /bin/date /bin/date.corrupt
	mv /tmp/date /bin/

This assumes that cp and mv are still good.


Richard