Hi, On Wed, Oct 04, 2006 at 12:28:37PM +0200, Richard van den Berg wrote: > What I did to try and work around the issue is close aide.db as soon as > possible (before the reporting is done). So basically, when a > report (with or without differences found) is printed you will know > gzclose() has been called, and the aide.db.new normally closed. This > change is now in CVS and will be in aide-0.12-rc2.
I'm going to package aide 0.12-rc2 for experimental as soon as possible. Since Debian is going to freeze on October 18, we will be releasing with aide 0.11 though. > Another important thing to note is that the real problem (the aide.db > being corrupted) occurs in the "aide --update" before the "aide > --update" (or "aide --check") that reports the many added files. It > would be very interesting to see an "aide -V255 --update" that actually > created the corrupt aide.db.new. I am trying to reproduce this on a host that will go out of service on October 31 and is not being used productively any more. I hope that I will be able to deliver the logs you need. Greetings Marc -- ----------------------------------------------------------------------------- Marc Haber | "I don't trust Computers. They | Mailadresse im Header Mannheim, Germany | lose things." Winona Ryder | Fon: *49 621 72739834 Nordisch by Nature | How to make an American Quilt | Fax: *49 621 72739835 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
