Hey,
We're running into an issue with testing file ages that come back as "4294967293" (which is '-1' or "2^32 -1")...for example:
File was modified 4294967293 seconds ago - should be <7200
I'm fairly certain I know why. On systems where you are checking for a large number of files and those files are being moved/deleted actively, it is possible for xymon to get the list of files and those files disappear before it can iterate over the list to stat the files to get the relevant info. This is similar to when you use rsync and it complains that files "vanished" before they could be transferred. I think this may be exasperated by using a command to find files.
I haven't looked in the code (nor would I know how to fix it if I did) but I would say that the 'stat' for the file should dump a "file vanished" message rather than give a "bogus" time stamp. Or the conditional could allow compound or 'ignore if' functions. I doubt I'm the only one running into this. It's causing many false alerts.
?
Putting it out there for awareness (and the hopes that someone has already sent JC a patch that just hasn't made it into Xymon yet).
=G=