this may be unrelated, but is this a new box? if not, did it have some kind of strange problems before? motivation for these questions: I once suspected a rooted box, since md5 sums of some system binaries changed. It was not rooted, it had a VIA (FIXME-don't remember the number) southbridge. and under heavy io it had single bitflips. yes. sometimes only on read, and then each read gave different results, sometimes on write too, so it really corupted data. workaround: switch off DMA access. (no fun on production machines) solution: change chipset. there may be similar hardware problems causing the effects you see. I don't say VIA boards are bad hardware. they are not. I just report what I experienced. /Lars On Tue, Jul 09, 2002 at 07:03:00PM +0200, ic_admin wrote:
I'm running tripwire to check my system each night, now I have a file which appears in my tripwire result as changed: /usr/lib/libc_nonshared.a But I didn't changed it! And in the tripwire-result I can only see the md5 and snefru sig's and NO st_mtime and NO st_ctime is displayed!
The next night I run the tripwire-system again and now the result is OK without creating a new database!? [ ... more the like ... ]