Hi everyone while the time is gotten down its still taking very long about
3 to 4 days to complete. I've been looking at the verbose reports but most
of it just shows the files being digested without really wha tmight be the
problem I can post but I'm not sure how useful it would be. My boss
Hi I wanted to clear up my confusion about how aide works. Does the aide
--check command work if there is no aide.conf. when a check is run then it
won't run right?
Also I just wanted to check that the aide check doesn't update the conf
every time a check happens. I believe that it only updates
On 08-09-13 10:10, Mason Nakadomari wrote:
Hi I wanted to clear up my confusion about how aide works. Does the
aide --check command work if there is no aide.conf. when a check is
run then it won't run right?
If there is no config file, aide does not know which files to scan with
which rules.
On 08-09-13 09:30, Mason Nakadomari wrote:
However the scans still take 3 to 4 days to complete and generate
reports 143000 lines long. Is there anyway I can speed this up or is
cutting down on files the only way.
Aide is typically IO bound on modern systems. Such long run times
indicate
here is what my iostat looks on the local machine. Could it be network
related since I'm running the aide-server package.
[root@aid70 ~]# iostat -dx
Linux 2.6.32-358.el6.x86_64 (aid70.pvt.hawaii.edu) 09/08/13
_x86_64_(1 CPU)
Device: rrqm/s wrqm/s r/s w/s rsec/s
On 8-9-13 14:19 , Mason Nakadomari wrote:
I am running it as nohup aide.init hostname would that make a
difference?
No, that does not make any difference.
Kind regards,
Richard
___
Aide mailing list
Aide@cs.tut.fi
On 8-9-13 14:40 , Mason Nakadomari wrote:
here is what my iostat looks on the local machine. Could it be network
related since I'm running the aide-server package.
IO performance can absolutely be network related when you are using a
SAN. I don't know what the aide-server package is though.
