Date: Sun, 2 Nov 1997 21:24:08 -1000 From: richard@pegasus.com (Richard Foulk) To: FreeBSD Questions <freebsd-questions@FreeBSD.ORG>, FreeBSD Hardware <freebsd-hardware@FreeBSD.ORG> Subject: Re: programs dying with SIGBUS after long uptime 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)
next in thread | previous in thread | raw e-mail | index | archive | help
} } 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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199711030724.VAA05159>