Add millisecond resolution to log timestamps
This change adds millisecond resolution to the timestamp written
on RMR stderr messages.
The change also allows the verbose control file specified by the
environment variable RMR_VCTL_FILE to be created and populated
after the application starts. In addition, if no variable is
supplied, RMR will now use a default control file (/tmp/rmr.v)
to allow debugging to be enabled without requireing an application
restart.
Issue-ID: RIC-627
Signed-off-by: E. Scott Daniels <daniels@research.att.com>
Change-Id: I207150679370add11fcdeef381ff453b28e701db
diff --git a/CHANGES_CORE.txt b/CHANGES_CORE.txt
index e59da47..5be9139 100644
--- a/CHANGES_CORE.txt
+++ b/CHANGES_CORE.txt
@@ -5,7 +5,19 @@
# API and build change and fix summaries. Doc corrections
# and/or changes are not mentioned here; see the commit messages.
-2021 January21; Version 4.5.2
+2021 February 08; Version 4.6.0
+ Enhanced to use millisecond based timestamps when writing log messages.
+ (RIC-627)
+
+ Enhanced to eliminate the reqirement that the file specified by the
+ RMR_VCTL_FILE environment variable exist when RMR is initialised. RMR
+ will correctly find this file if it is created after initialisation.
+ Further, if the environment variable is not given, the user may create
+ and populate /tmp/rmr.v at any time and the contents of this file will
+ be used as if it were supplied via the environment variable. This should
+ make debugging in existing containers easier.
+
+2021 January 21; Version 4.5.2
Fixes the excessive TCP session bug when sending to a slow receiver
and a related segment fault because of too many open file descriptors.
(RIC-735)