Time units are misleading in warning message

[matt-beall]

When a reading violates the latency limit, a warning message is posted to the log. This message states the latency and the desired latency. Actual latency is in seconds, and desired is in milliseconds, but the message compares them and is stated in seconds.

Example:

Oct 21 10:42:03 XXXX[1145]: WARNING: Current send latency of XXXXX seconds exceeds requested maximum latency of 5000 seconds

[MarkRiddoch]

Thanks for pointing this out Matt. We now have a fix for this in the develop branch and also in the nightly build available via the package repository. This will be rolled out int he next release later this year.