summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorErlang/OTP <otp@erlang.org>2012-06-13 18:57:14 +0200
committerErlang/OTP <otp@erlang.org>2012-06-13 18:57:14 +0200
commitd2c7d9ffb3ceffdb324ce93fc2ea2f442f12c1fe (patch)
treee2ea5200d8fe04acac059013edb6835e93b1740b
parent3d0199a8a9d604aa7a22e996adfd249dddbdccf8 (diff)
downloaderlang-d2c7d9ffb3ceffdb324ce93fc2ea2f442f12c1fe.tar.gz
Prepare release
-rw-r--r--erts/doc/src/notes.xml24
-rw-r--r--erts/vsn.mk2
2 files changed, 25 insertions, 1 deletions
diff --git a/erts/doc/src/notes.xml b/erts/doc/src/notes.xml
index 09950e865b..8ff3f50348 100644
--- a/erts/doc/src/notes.xml
+++ b/erts/doc/src/notes.xml
@@ -30,6 +30,30 @@
</header>
<p>This document describes the changes made to the ERTS application.</p>
+<section><title>Erts 5.7.5.3</title>
+
+ <section><title>Fixed Bugs and Malfunctions</title>
+ <list>
+ <item>
+ <p>
+ On Linux systems using heart (erl -heart) and a
+ HEAR_BEAT_TIMEOUT less than default, heart could fire
+ even though Erlang was running fine after approx 298 to
+ 497 days (depending on kernel config). This was due to
+ the behaviour of the times(2) system call. Usage of
+ times(2) is now replaced with clock_gettime(2) and the
+ CLOCK_MONOTONIC clock, resulting in a more stable
+ solution. The Erlang VM itself has used clock_gettime(2)
+ on linux since before R12B, so this only affects the
+ heart program.</p>
+ <p>
+ Own Id: OTP-10111 Aux Id: seq12075 </p>
+ </item>
+ </list>
+ </section>
+
+</section>
+
<section><title>Erts 5.7.5.2</title>
<section><title>Known Bugs and Problems</title>
diff --git a/erts/vsn.mk b/erts/vsn.mk
index 4e6571c70b..2e830150d8 100644
--- a/erts/vsn.mk
+++ b/erts/vsn.mk
@@ -17,7 +17,7 @@
# %CopyrightEnd%
#
-VSN = 5.7.5.2
+VSN = 5.7.5.3
SYSTEM_VSN = R13B04
# Port number 4365 in 4.2