Some problems seem to be difficult to reproduce between different users and systems. LAG probably needs a mechanism for logging events and problems for post-mortem analysis.
- Trivial events need to be logged on a regular basis. The system needs to either be efficient, or have the option to be enabled/disabled, perhaps with a command-line argument.
- The system needs to be threadsafe. Time constraints mean per-use-case thread management is not an option.
- The logging system cannot reflect the functionality that usleep served previously, that is, the system must behave the same with logging as it does without logging. If a slowdown occurs, many race-conditions could easily be suppressed just by enabling logging.
Some problems seem to be difficult to reproduce between different users and systems. LAG probably needs a mechanism for logging events and problems for post-mortem analysis.