Another possibility is bad memory -- if this is on an x86 machine with non-parity memory (or even if it is) I'd recommend getting memtest86 from http://www.memtest86.com/ and running it. Definitely do this if you can reboot the machine and it appears to go back to the old checksum.
Jim On Tue, Jan 08, 2002 at 08:32:18AM -0500, Jake Colman wrote: > > Last night's tripwire report shows me the following: > > Modified object name: /usr/sbin/nmbd > > Property: Expected Observed > ------------- ----------- ----------- > * CRC32 Bxg0hX AZ+PIg > * MD5 C7FzKDjQBMyVi/wKwNKkmI DvNlgaBlMV2gQRCQNROrxg > > What could cause this other than someone hacking it and changing the binary? > I am running an iptables-based firewall so I would be surprised if something > like this has happened. > > Any suggestions? _______________________________________________ Redhat-list mailing list [EMAIL PROTECTED] https://listman.redhat.com/mailman/listinfo/redhat-list
