&<caiUxsA2.308>Default monitor condition for the modification monitoring of the file watcher to add. As basis for the comparison the user can choose between modification time, change time, change time only (change time is modified and modification time is not) and access time. The timestamps can be monitored for being modified (should-be-modified, should-be-changed, should-be-changed-only, should-be-accessed) or for being unmodified (should-not-be-modified, should-not-be-changed, should-not-be-changed-only, should-not-be-accessed). At each poll the current timestamp of the file will be compared with the reference timestamp according to the chosen policy. For one-to-many watchers the latest timestamp of all files is considered. If monitoring is for being modified the status is down if the file was not modified for more seconds than the value of 'FileModInterval'. If monitoring is for being unmodified the status is down if the file was modified more often than every 'FileModInterval' seconds. If 'FileModInterval' is zero any modification sets the status down. If the monitor status is 'down' and the monitoring condition is met at the next poll the status of the watcher will revert to up (automatic repair). However, the metric may be reset manually at any time by setting the monitor condition to reset-time-reference. Afterwards the previous policy setting is restored. Note: if the policy is set to should-not-xxx and 'FileModInterval' is 0, no automatic repair takes place. This behaviour is for compatibility with the old UNIX System Agent (caiUxOs). Note that status evaluation only takes place when the agent polls. Thus the end of the modification interval will be detected on the subsequent poll or query.