aboutsummaryrefslogtreecommitdiffstats
path: root/lib/sasl/doc
diff options
context:
space:
mode:
authorPaul Guyot <pguyot@kallisys.net>2010-06-06 22:26:08 +0200
committerSiri Hansen <siri@erlang.org>2011-02-25 14:37:07 +0100
commit49d011c355682ce5cb5447c682684031dab82e8b (patch)
treee170f8d7c0762b62264ea61c2c7efea59961d608 /lib/sasl/doc
parent5e354ca66996ee03d615dc36c284e94ccf176e89 (diff)
downloadotp-49d011c355682ce5cb5447c682684031dab82e8b.tar.gz
otp-49d011c355682ce5cb5447c682684031dab82e8b.tar.bz2
otp-49d011c355682ce5cb5447c682684031dab82e8b.zip
Honor start type in .rel files when building relup files
Previously, relup file always included an application:start(Application, permanent) apply instruction for every application that appear in the UpTo/DowFrom release file, whatever their start type in the release file. The new implementation fixes this bug by honoring the start type according to the rel(5) format. If the start type is none, no apply line is included in the relup. If the start type is load, the relup includes instruction to only load the application. Otherwise, the relup includes an instruction to start the application to the according type. The fix is implemented by adding a new parameter to the add_application high level appup instruction. This new parameter is documented in appup(5).
Diffstat (limited to 'lib/sasl/doc')
-rw-r--r--lib/sasl/doc/src/appup.xml10
1 files changed, 9 insertions, 1 deletions
diff --git a/lib/sasl/doc/src/appup.xml b/lib/sasl/doc/src/appup.xml
index 5182889710..48d7b69885 100644
--- a/lib/sasl/doc/src/appup.xml
+++ b/lib/sasl/doc/src/appup.xml
@@ -174,11 +174,19 @@
<c>remove</c> and <c>purge</c>.</p>
<pre>
{add_application, Application}
+{add_application, Application, Type}
Application = atom()
+ Type = permanent | transient | temporary | load | none
</pre>
<p>Adding an application means that the modules defined by
the <c>modules</c> key in the <c>.app</c> file are loaded using
- <c>add_module</c>, then the application is started.</p>
+ <c>add_module</c>.</p>
+ <p><c>Type</c> defaults to <c>permanent</c> and specifies the start type
+ of the application. If <c>Type = permanent | transient | temporary</c>,
+ the application will be loaded and started in the corresponding way,
+ see <c>application(3)</c>. If <c>Type = load</c>, the application will
+ only be loaded. If <c>Type = none</c>, the application will be neither
+ loaded nor started, although the code for its modules will be loaded.</p>
<pre>
{remove_application, Application}
Application = atom()