1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
|
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<!-- This document was generated using DocBuilder 3.3.2 -->
<HTML>
<HEAD>
<TITLE>Sasl Release Notes
</TITLE>
<SCRIPT type="text/javascript" src="../../../../doc/erlresolvelinks.js">
</SCRIPT>
</HEAD>
<BODY BGCOLOR="#FFFFFF" TEXT="#000000" LINK="#0000FF" VLINK="#FF00FF"
ALINK="#FF0000">
<CENTER>
<A HREF="http://www.erlang.se"><IMG BORDER=0 ALT="[Ericsson AB]" SRC="min_head.gif"></A>
</CENTER>
<A NAME="1"><!-- Empty --></A>
<H2>1 Sasl Release Notes
</H2>
<P>This document describes the changes made to the Sasl application.
<A NAME="1.1"><!-- Empty --></A>
<H3>1.1 Sasl 2.0</H3>
<A NAME="1.1.1"><!-- Empty --></A>
<H4>1.1.1 Fixed Bugs and Malfunctions</H4>
<P>
<UL>
<LI>
When doing a code replacement in run-time, updating the
internal state of a gen_server, gen_event or gen_fsm, it
was stated in the documentation that the first argument
<CODE>OldVsn</CODE> to the callback function
<CODE>Module:code_change</CODE> was defined by the <CODE>vsn</CODE>
attribute in the old version of <CODE>Module</CODE>.
<BR>
However, this was not true. For downgrades, <CODE>OldVsn</CODE>
was <CODE>{down,Vsn}</CODE>, where <CODE>Vsn</CODE> was fetched from
the <CODE>.app</CODE> file instead.
<BR>
The version is now always fetched from the module using
<CODE>beam_lib:version/1</CODE> and the man pages for gen_*
have been updated accordingly.
<BR>
*** POTENTIAL INCOMPATIBILITY ***
<BR>
Own Id: OTP-3699
<BR>
</LI>
<LI>
The release handling instruction
<CODE>restart_application</CODE> was translated to the
low-level instruction <CODE>application_remove</CODE> and a set
of <CODE>load_module</CODE> instructions.
<BR>
However, <CODE>application_remove</CODE> caused the modules
listed for the new, not the old, version of the
application to be unloaded. If the set of modules was
changed, this meant the release handler would try to
purge non-existant modules and/or forget to unload
modules no longer used.
<BR>
<CODE>restart_application</CODE> is now translated to a correct
set of <CODE>delete_module</CODE> and <CODE>add_module</CODE>
instructions instead, and the <CODE>application_remove</CODE>
instruction is deprecated.
<BR>
*** POTENTIAL INCOMPATIBILITY ***
<BR>
Own Id: OTP-4805
<BR>
</LI>
<LI>
<CODE>release_handler:check_install_release/1</CODE> returned
<CODE>{error,Reason}</CODE> if <CODE>sys.config</CODE> or
<CODE>relup</CODE> was missing. Since both these files are
optional, the behaviour has been changed to write
warnings to the terminal but return an <CODE>ok</CODE> tuple
instead.
<BR>
*** POTENTIAL INCOMPATIBILITY ***
<BR>
Own Id: OTP-4824
<BR>
</LI>
</UL>
<A NAME="1.1.2"><!-- Empty --></A>
<H4>1.1.2 Improvements and New Features</H4>
<P>
<UL>
<LI>
Added a clause to <CODE>systools:make_script/1</CODE> which
makes it possible to provide (atomic) options when
calling the function using <CODE>erl -s</CODE>.
<BR>
Example: <CODE>erl -noinput +B -s systools make_script myrel
no_module_tests -s erlang halt</CODE> is equal to calling
<CODE>systools:make_script("myrel", [no_module_tests])</CODE>.
<BR>
Own Id: OTP-3384
<BR>
</LI>
<LI>
Added simplified versions of the <CODE>update</CODE> and
<CODE>load_module</CODE> release handling instructions.
<BR>
Own Id: OTP-4793
<BR>
</LI>
<LI>
Added two new release handling instructions: <CODE>{update,
Module, supervisor}</CODE> and <CODE>{delete_module,
Module}</CODE>
<BR>
Own Id: OTP-4800
<BR>
</LI>
</UL>
<A NAME="1.2"><!-- Empty --></A>
<H3>1.2 Sasl 1.10.1</H3>
<A NAME="1.2.1"><!-- Empty --></A>
<H4>1.2.1 Improvements and New Features</H4>
<P>
<UL>
<LI>
The option {abort_on_error,Bool} has been added to
rb:start/1 and rb:rescan/1. With it you can choose
whether or not rb should stop logging if it encounters an
unprintable report. When abort_on_error is set to false,
rb will resume logging after a bad report has been
handled. The error messages rb prints when logging fails
have been enhanced.
<BR>
Own Id: OTP-5096 Aux Id: seq8930
<BR>
</LI>
</UL>
<CENTER>
<HR>
<SMALL>
Copyright © 1991-2004
<A HREF="http://www.erlang.se">Ericsson AB</A><BR>
</SMALL>
</CENTER>
</BODY>
</HTML>
|
