[Aide] Problems with AIDE on Debian Sarge (0.10).

[Bob Proulx]

Virgo Pärna wrote:
> 	I think I have the reason and it does not seem to be the faul of AIDE.
> I think, that when I redirect aide output to less and then scroll it to
> see what as changed and then quit from less, the aide is not always
> completed but is aborted?

Less will read the input as it goes.  If you quit less before less has
seen the end of file from the process feeding the pipe then that other
process will get a SIGPIPE and stop.  That's normal for most programs.

When I want any program in general to run to completely but still want
to scroll around in the output then the very first thing I do in less
is to hit the 'G' key.  That seeks to end of file.  At that point the
input has stopped.  Then I can scroll around without fear because I am
only looking at data bufferred in less memory.

But I had never even considered doing that with aide output.

> It seems to be most likely reason to me (I got same problem with CVS
> version also). I should probably use more to scroll AIDE output -
> more quits by itself, when input ends and does not need quiting
> specially.

I believe that you would see the same problem with more if you quit
before it has seen the end of file.  Instead if you want to page use
the trick with 'G'.

But since I think this is error prone that means that even if you know
about this that you would sometimes leave a partial database behind.

Bob