What does TimeStamp mean on the scan reports?

[sneader]

At the top of our Scan Reports, it says (for example:

Code: Select all

----------- SCAN REPORT -----------
TimeStamp: Wed Apr 1 03:38:56 2015
(/usr/sbin/cxs --allusers --nobayes --clamdsock /var/clamd --defapache nobody 
(snip)

The TimeStamp above is from April 1st, but the scan was just completed this afternoon (April 6). I don't yet understand the date difference.

I see in the Change Log where the TimeStamp was added, but I don't know what TimeStamp means. The only idea I have is that it might be the date/time of the last signature update?

I tried to grep through the various cxs directories for "TimeStamp" but came up empty. Help?

- Scott

[ForumAdmin]

It's the time taken from the server when the command was initiated.

[sneader]

Thanks for the quick reply. I seem to be missing a setting on the board to alert me by email when topics have activity.

Anyway, back to the problem: Any ideas why these alerts would be sent 5-6 days after the "command was initiated"? I'm looking at the headers of the alerts, and it's not an email delivery problem... I'm getting the alerts right away. I'm trying to understand how the command could be initiated on April 1st, but CXS wouldn't send me an email until 5 days later? I'm very confused. :-(

- Scott

[sneader]

... is it possible that the Timestamp is when CXS Watch was started?

[ForumAdmin]

Ah! Yes it is, which makes it a bug. We'll look into it for the next release.

[ForumAdmin]

This should now be resolved in v5.22:
http://blog.configserver.com/

[sneader]

Super! Thank you!! So, now, what will the TimeStamp indicate? The time that CXS actually scanned that particular file?

- Scott

[ForumAdmin]

Yes