This document describes the changes made to the SASL application.
If sys.config existed, but was not readable or parseable, this would not be detected until after the upgrade and at the next node restart. The possibility for this to happen is now reduced by adding a check to systools:make_tar which fails the creation of the tar file if sys.config or relup does not have reasonable contents. Note that there are no detailed checks, only parsing and erlang term format check.
Own Id: OTP-9539
systools:make_script would allow {kernel,Vsn,load} in the .rel file, causing a .boot file which only loaded kernel and did not start it. This has been corrected. Only start type 'permanent', which is the default, is now allowed for kernel and stdlib.
Own Id: OTP-9652
release_handler:remove_release/1 now handles symlinked files properly
Own Id: OTP-9864
If stdlib was stated with a start type different from
Own Id: OTP-9888
Sasl documentation earlier said that the InclApps parameters in a .rel file defaults to the empty list. This is not correct. It defaults to the same value as specified in the .app file. This has been corrected.
Own Id: OTP-9980
Applications that are listed in
*** POTENTIAL INCOMPATIBILITY ***
Own Id: OTP-9984
Documentation of .appup files now also states that
Own Id: OTP-10001
Reltool would sometimes generate a .app file containing
In order to align with reltool, sasl will also omit
Own Id: OTP-10003
Fix the mechanism for upgrading emulator.
The appup files for kernel, stdlib and sasl do now recognize two major releases back and include a 'restart_new_emulator' instruction.
Appup files can include regular expressions for matching earlier releases.
The mechanism for upgrading the emulator is changed so 'restart_new_emulator' will be the first instruction executed. The rest of the upgrade instruction will be executed after the emulator restart.
A new upgrade instruction 'restart_emulator' is added for the case where the emulator shall be restarted after all other upgrade instructions.
*** POTENTIAL INCOMPATIBILITY ***
Own Id: OTP-9438
Add release_handler:which_releases/1
This is an extension to which_releases that allows a user to specify the status of the releases they wish to be returned. For instance it allows for quickly determining which release is 'permanent' without the need of parsing the entire release list. (Thanks to Joe Williams)
Own Id: OTP-9717
Add copy of rel file in releases/Vsn in release tar file
systool:make_tar stores the rel file in the releases directory. When unpacking with release_handler:unpack_release, the file is automatically moved to releases/Vsn/. If, however, the tar file is unpacked manually, the rel file might not be moved, and the next release unpacked might overwrite the rel file. To overcome this, systools:make_tar now stores a copy of the rel file in releases/Vsn/ directly and it is not longer necessary to move the file after unpacking.
The reason for keeping the file in the releases directory also is that is needs to be extracted separately before the release version (Vsn) is known.
Own Id: OTP-9746
The release_handler functionality on windows services was broken. This has been corrected.
Own Id: OTP-9306
If a new version of an application did not include any erlang module changes, the code path of the application was not updated by the release_handler unless a 'load_object_code' instruction was added for the application. This would be a problem if e.g. only some files in the priv dir were changed since calls to code:lib_dir or code:priv_dir would then point to the old location of the application. This has been corrected - now code:replace_path/2 will be called for all applications that are changed (i.e. when the application's vsn is changed in the .rel file).
Own Id: OTP-9402
The appup instruction 'delete_module' would cause a crash during upgrade if the module to be deleted was not loaded. This has been corrected.
Own Id: OTP-9417
If a path was given as ONLY 'ebin' and not for example
'./ebin', then systools:make_tar would fail with a
Own Id: OTP-9507
Implement or fix -Werror option
If -Werror is enabled and there are warnings no output file is written. Also make sure that error/warning reporting is consistent. (Thanks to Tuncer Ayaz)
Own Id: OTP-9536
Improved error information for timeouts during release_handler:install_release.
This patch addresses two cases where a timeout will occur during upgrade. 1) if a supervisor is suspended (call to get children from supervisor will hang) 2) if the child spec for a supervisor incorrectly states that it is a worker with a dynamic set of modules (call to get modules from gen_event will hang)
An error report will now be printed, and the return value of release_handler:install_release will indicate what happened. (Thanks to joe williams)
Own Id: OTP-9546
A new option,
Own Id: OTP-9395
Remove traces of release_handler reading from filesystem when it has Masters list
There are a couple of places in release_handler and release_handler_1 that assumed it has a disk to read from, which in the case of an erl_prim_loader Loader other than efile is not necessarily true
Add check_paths/2 to do the equivalent of check_path/1 for when there is a Masters list
Change get_vsn to no longer get sent File paths but instead use the Bin since beam_lib:version being sent a file path causes it to read the local file system
Add get_current_vsn/1 as an equivalent to beam_lib:version(code:which(Mod)), but using erl_prim_loader:get_file instead of reading from local file system
(Thanks to Steven Gravell)
Own Id: OTP-9142
rb:stop did sometimes return {error,running}. This came from supervisor:delete_child and happened when the rb_server has not yet terminated when this function was called. Instead of having a separate gen_server call to rb_server for stopping the process, supervisor:terminate_child is now called. This is a synchronous function - i.e. it waits for the process to actually terminate before it returns.
A file descriptor leak in rb:scan_files is corrected. The index file was never closed after reading.
A mismatch in the behavior of rb:filter, when filter included 'no', is corrected. Such filters will now return *all* non-matching reports, not only the 'proplist' reports.
Own Id: OTP-9149
Start and end date for rb:filter/2 was specified as {{Y-M-D},...} in the help text instead of {{Y,M,D},...}. This has been corrected.
Own Id: OTP-9166
If some, but not all, of the sasl environment variables related to the log_mf_h error handler were missing sasl would successfully start but silently skip starting log_mf_h. This is corrected so sasl startup will now fail if one or two of the three variables are given. If none of the variables are given, sasl will start as before without starting log_mf_h.
Own Id: OTP-9185
Change default behaviour to not check src code when creating release
Add new option
*** POTENTIAL INCOMPATIBILITY ***
Own Id: OTP-9146 Aux Id: seq11803
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).
Own Id: OTP-9097
In R13B04 sys:get_status was modified to invoke format_status/2 in the callback module if the module exports that function. This resulted in a change to the term returned from calling sys:get_status on the supervisor module, since supervisor is a gen_server and gen_server exports format_status. The sasl release_handler_1 module had a dependency on the pre-R13B04 term returned by sys:get_status when invoked on a supervisor, so the R13B04 change broke that dependency.
This problem has been fixed by change release_handler_1 to handle both the pre-R13B04 and R13B04 terms that sys:get_status can return from a supervisor.
Own Id: OTP-8619 Aux Id: seq11570
Use an infinity timeout in all calls to
Own Id: OTP-8506 Aux Id: seq11509
The
Own Id: OTP-8443
There is new function
Own Id: OTP-8445
Cleanups suggested by tidier and modernization of types and specs.
Own Id: OTP-8455
The documentation is now built with open source tools (xsltproc and fop) that exists on most platforms. One visible change is that the frames are removed.
Own Id: OTP-8201
The Windows utility Erlsrv, run in interactive mode now accepts options for registering internal service name and description field of Windows registry database.
Own Id: OTP-8132
When using the SASL application configuration
parameter
Own Id: OTP-7667
Missing preloaded modules added
Own Id: OTP-7820
A Dialyzer warning was eliminated
Own Id: OTP-7635
Minor changes.
Own Id: OTP-7388
Minor updates.
Own Id: OTP-6998
Minor Makefile changes.
Own Id: OTP-6689
Obsolete guard tests (such as list()) have been replaced with the modern guard tests (such as is_list()).
Own Id: OTP-6725
Removed some dead code from
Own Id: OTP-6499
Added an option
Also, when using
As part of the work some minor bugs have been corrected:
A documentation error for
Own Id: OTP-6226
Own Id: OTP-6162
Fixed some minor bugs in
Own Id: OTP-6039
Added a number of functions to
-
-
-
-
-
Own Id: OTP-5858
A new option
*** POTENTIAL INCOMPATIBILITY ***
Own Id: OTP-5761
A bug that made it impossible to call
Own Id: OTP-5287