Scenarios

This list shows the scenarios that can happen:

1. When the start_blogind_tracing file is present on a local and shared location, the file with the latest timestamp, the creation date, is used.
2. If the content of the start_blogind_tracing is invalid, the file is ignored with no effect on tracing. The file is not used again for enabling or disabling tracing.
3. If there is no start_blogind_tracing file, or the file is removed, the tracing continues in its current state.
4. If the start_blogind_tracing file is placed on a tracing enabled login server, the tracing stops after the specified duration time has passed.
5. To stop the tracing, the fastest way is to specify 1M in the start_blogind_tracing file and save it in either location. To stop debugging or tracing on all the hosts you must change and save the file in the shared location. All hosts that run the logic service with the specified shared location in their resource file are stopped.
6. When the logic server is started, it searches for the latest start_blogind_tracing file. When the file is found the tracing is started until the specified duration time is not passed and vice versa.