Skip to content

The synchronous and pause options on run

Nat! edited this page Feb 15, 2018 · 1 revision

The callback is supposed to determine a task and return quickly. The callback is run synchronously. The task is then run asynchronously. The dispatch of the task should be fast enough.

But there is no guarantee that the callback is fast, due to it being external, and maybe sometimes it may make sense to write a slow callback. In a scenario like this you can use the --pause option to stop the monitor during callback/task processing and resume afterwards. The downside of this is, that events can be lost. Tasks would still be run asynchronously in this scenario.

You can also force the task to run synchronously with the --synchronous option. This may work in scenarios, where there are not a lot of events created.

Clone this wiki locally