An update basically is an --init with a --compare to the old database.
When aide does a compare, it builds a tree for the new db, and removes
all files from the old db from that tree (and checks if they should be
reported as changed). When that process has finished, all files still in
the tree
On Mon, Mar 13, 2006 at 09:13:01AM +0100, Richard van den Berg wrote:
> Last week I saw something similar on one of my systems. The problem was
> with my aide.db.gz being corrupted (bad block on fd0). I don't think the
> same issue applies here, but it might have to do with aide not reading
> in
On Fri, Jul 28, 2006 at 03:11:07PM -0600, Will Aoki wrote:
> It took me a while (the problem mysteriously disappeared for a while on
> my machines that still use aide), but here's the output. The changes
> (/var/cfengine, et cetara) are correct, but the additions are not.
> $ sudo aide --compare -
On Tue, Dec 12, 2006 at 04:18:25PM +0100, Marc Haber wrote:
> After going through another update round, changing both upstream aide
> and the aide cron job, can you guys please re-try with aide 0.13 from
> Debian testing (it backports nicely if you're running stable) and
> gzip_dbout enabled?
I wa
On Fri, Apr 23, 2004 at 01:54:57PM +1000, Pete de Zwart wrote:
> After doing a:
>
> aide --update
>
> mv /var/lib/aide/aide.db.new /var/lib/aide.db
>
> aide --check
>
> All the files in /sbin are declared as "added", which seems a bit odd,
> sometimes a further --update cycle will fix it, somet
user [EMAIL PROTECTED]
usertags #245423 close-20070331
thanks
On Tue, Dec 12, 2006 at 04:18:25PM +0100, Marc Haber wrote:
> After going through another update round, changing both upstream aide
> and the aide cron job, can you guys please re-try with aide 0.13 from
> Debian testing (it backports n
6 matches
Mail list logo