Server Fault is a question and answer site for system and network administrators. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

I have set my auditd rules to log when the system time is changed

However, our servers are VMs and thus have problems with the time drifting out. We needed to solve this issue so we used a VMware tool to regularly synchronize the time.

My problem now is that my audit logs are overwhelmed with time change entries like this:

Jun  1 15:08:39 ***** audispd: node=****** type=SYSCALL
arch=c000003e syscall=159 success=yes exit=5 a0=7ffff2084050 a1=0 a2=144b
a3=485449575f4c4c55 items=0 ppid=1 pid=1348 auid=4294967295 uid=0 gid=0 
euid=0 suid=0 fsuid=0 egid=0 sgid=0 fsgid=0 tty=(none) ses=4294967295 
comm="vmtoolsd" exe="/usr/lib/vmware-tools/bin64/appLoader" key="time_change"

How can I exclude this vmware tool from the audit, but still capture a user changing the time?

Here are my current audit rules to capture time changes:

-a always,exit -F arch=b32 -S adjtimex -S settimeofday -k time_change
-a always,exit -F arch=b32 -S clock_settime -k time_change
share|improve this question
up vote 1 down vote accepted

If I've understood correctly, you're monitoring the kernel time change events. I see no direct method to prevent a single tool from appearing in the logs but I have two possible workarounds:

  1. Simply filter the log before reviewing the audit log. Perl or awk are your friends, or
  2. Use a custom script (e.g. in /etc/cron.d/) which turns the time audit off, updates the time, and then again turns the time audit on.

Unless your logs are too big for the storage device you're using, I'd prefer option 1 because that keeps full audit log and you're simply removing the parts you're not interested in by the time you're reviewing the audit log. Those automatic time changes are part of the reality and may be needed to interpret timestamps in the audit log in case of severe time drift near an occurrence of interesting audit event (hopefully your time adjustment software logs the adjusted amount of time so you can then later manually resync the time in the logs, if needed).

share|improve this answer

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.