Dumps trace information to the console for timestamp maintenance on any outstanding archive locks and the discovery of timestamp changes on locks maintained by other servers.
An archive lock is created by placing a lock file into an appropriate directory. In order for the lock to persist, the timestamp on the file must change periodically; otherwise any contending Content Server will treat the lock as an expired lock.
There is no default setting.
Note:This variable is obsolete as of the Content Server 7.0 release. The functionality is now available in the System Audit Information page.
As a configuration setting: