From e6ea3b07e25b09481b010558f8bfdfb57dcbb85e Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Bj=C3=B6rn-Egil=20Dahlberg?= Date: Mon, 15 Oct 2012 16:22:47 +0200 Subject: doc: Document ERL_CRASH_DUMP_SECONDS behaviour * heart reboot behaviour * erl_crash.dump file write behaviour --- lib/kernel/doc/src/heart.xml | 33 +++++++++++++++++++++++++++++++++ 1 file changed, 33 insertions(+) (limited to 'lib/kernel/doc/src/heart.xml') diff --git a/lib/kernel/doc/src/heart.xml b/lib/kernel/doc/src/heart.xml index 26d1e27822..2826d3d00a 100644 --- a/lib/kernel/doc/src/heart.xml +++ b/lib/kernel/doc/src/heart.xml @@ -71,6 +71,39 @@ timeout and try to reboot the system. This can happen, for example, if the system clock is adjusted automatically by use of NTP (Network Time Protocol).

+ +

If a crash occurs, an will not be written + unless the environment variable is set. +

+ +
+% erl -heart -env ERL_CRASH_DUMP_SECONDS 10 ...
+

+ Furthermore, has the following behaviour on + heart: +

+ + +

+ Suppresses the writing a crash dump file entirely, + thus rebooting the runtime system immediately. + This is the same as not setting the environment variable. +

+
+ +

Setting the environment variable to a negative value will not reboot + the runtime system until the crash dump file has been completly written. +

+
+ +

+ Heart will wait for S seconds to let the crash dump file be written. + After S seconds heart will reboot the runtime system regardless of + the crash dump file has been written or not. +

+
+
+

In the following descriptions, all function fails with reason badarg if heart is not started.

-- cgit v1.2.3