To build an upload, dbmlsync must scan the transaction log. Usually it does this just before synchronization. However, when
synchronizations are scheduled or the sp_hook_dbmlsync_delay hook is used, dbmlsync by default scans the log in the time between
synchronizations. This behavior is more efficient because the log is already at least partially scanned when synchronization
begins. This default behavior is called logscan polling.
Logscan polling is on by default but only has an effect when synchronizations are scheduled or when sp_hook_dbmlsync_delay
hook is used. When in effect, polling occurs at set intervals: dbmlsync scans to the end of the log, waits for the polling
period, and then scans any new transactions in the log. By default, the polling period is 1 minute, but it can be changed
with the dbmlsync -pp option or the PollingPeriod extended option.
The default is to not disable logscan polling (OFF).