Erlang -- SASL Release Notes

User's Guide
Reference Manual
Release Notes
PDF
Top

System Application Support Libraries (SASL)
Release Notes
Version 2.1.10

Expand All
Contract All

Chapters

- SASL Release Notes
  - Top of chapter
  - SASL 2.1.10
  - SASL 2.1.9.4
  - SASL 2.1.9.3
  - SASL 2.1.9.2
  - SASL 2.1.9.1
  - SASL 2.1.9
  - SASL 2.1.8
  - SASL 2.1.7
  - SASL 2.1.6
  - SASL 2.1.5.4
  - SASL 2.1.5.3
  - SASL 2.1.5.2
  - SASL 2.1.5.1
  - SASL 2.1.5
  - SASL 2.1.4
  - SASL 2.1.3
  - SASL 2.1.2
  - SASL 2.1.1
  - SASL 2.1
  - SASL 2.0.1

# 1 SASL Release Notes

This document describes the changes made to the SASL application.

### 1.1 SASL 2.1.10

#### Fixed Bugs and Malfunctions

- 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 function_clause exception in filename:join/1. This has been corrected. (Thanks to Nikola Skoric for reporting).

  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

#### Improvements and New Features

- release_handler:install_release could be very slow when there are many processes in the system. Some optimization work has been done both in erts and in the release handler in order to improve this.

  A new option, purge, is added to release_handler:check_install_release which can be called first in order to speed up the execution of release_handler:install_release.

  Own Id: OTP-9395

### 1.2 SASL 2.1.9.4

#### Fixed Bugs and Malfunctions

- 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

#### Improvements and New Features

- Change default behaviour to not check src code when creating release

  Add new option src_tests to systools:make_script and systools:make_tar. The old option no_module_tests is now ignored as this is the default behaviour.

  *** POTENTIAL INCOMPATIBILITY ***

  Own Id: OTP-9146 Aux Id: seq11803

### 1.3 SASL 2.1.9.3

#### Improvements and New Features

- 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

### 1.4 SASL 2.1.9.2

#### Fixed Bugs and Malfunctions

- 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

### 1.5 SASL 2.1.9.1

#### Improvements and New Features

- Use an infinity timeout in all calls to gen_server:call() in the sasl application.

  Own Id: OTP-8506 Aux Id: seq11509

### 1.6 SASL 2.1.9

#### Improvements and New Features

- The re:grep/1 function now uses the 're' module instead of the deprecated 'regexp' module. There are new functions rb:filter/1 and rb:filter/2 for easier filtering of reports. (Thanks to Alvaro Videla.)

  Own Id: OTP-8443

- There is new function sasl_report:format_report/3 that works like the existing sasl_report:write_report/3 function except that it returns a formatted string. Note that there is currently no documentation for the sasl_report module. (Thanks to Jay Nelson.)

  Own Id: OTP-8445

- Cleanups suggested by tidier and modernization of types and specs.

  Own Id: OTP-8455

### 1.7 SASL 2.1.8

#### Improvements and New Features

- 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

### 1.8 SASL 2.1.7

#### Improvements and New Features

- 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

### 1.9 SASL 2.1.6

#### Fixed Bugs and Malfunctions

- When using the SASL application configuration parameter masters the error tuple {error,{no_such_file,{Master,FileName}}} was sometimes returned even though the file FileName existed.

  Own Id: OTP-7667

#### Improvements and New Features

- Missing preloaded modules added

  Own Id: OTP-7820

### 1.10 SASL 2.1.5.4

#### Improvements and New Features

- A Dialyzer warning was eliminated

  Own Id: OTP-7635

### 1.11 SASL 2.1.5.3

#### Improvements and New Features

- Minor changes.

  Own Id: OTP-7388

### 1.12 SASL 2.1.5.2

#### Improvements and New Features

- Minor updates.

  Own Id: OTP-6998

### 1.13 SASL 2.1.5.1

#### Improvements and New Features

- 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

### 1.14 SASL 2.1.5

#### Fixed Bugs and Malfunctions

- Removed some dead code from erlsrv:get_service/2, release_handler:do_write_file/2, systools_relup:foreach_baserel_up/7 and systools_relup:foreach_baserel_dn/7.

  Own Id: OTP-6499

### 1.15 SASL 2.1.4

#### Improvements and New Features

- Added an option {outdir,Dir} to the functions in systools, making it possible to specify in which directory a boot script, relup file or release package file should be placed.

  Also, when using systools:make_tar/2 to create a release package file, the boot script, relup file and sys.config are now searched for also in the current working directory and any directory specified by the path option, not only in the directory of the .rel file.

  As part of the work some minor bugs have been corrected:

  - systools:make_script/1,2 now returns error if the .script and/or .boot file could not be opened for writing, not ok.

  - systools:make_tar/1,2 can now handle a RelName argument which includes a path. Previously this would cause the .rel file to end up in the wrong directory in the resulting tar file.

  - A documentation error for systools:make_tar/1,2: The .rel file is placed in the releases directory in the tar file, not releases/RelVsn.

  Own Id: OTP-6226

### 1.16 SASL 2.1.3

#### Fixed Bugs and Malfunctions

- release_handler:upgrade_app/2 and release_handler:downgrade_app/2,3 -- used for testing application upgrade and downgrade according to the .appup file -- now update application configuration parameters correctly. (Thanks to Serge Aleynikov)

  Own Id: OTP-6162

### 1.17 SASL 2.1.2

#### Fixed Bugs and Malfunctions

- Fixed some minor bugs in release_handler found by Dialyzer.

  Own Id: OTP-6039

### 1.18 SASL 2.1.1

#### Improvements and New Features

- Added a number of functions to release_handler which makes it possible to test upgrade and downgrade of applications according to an .appup file "on the fly":
  - upgrade_app/2
  - upgrade_script/2
  - downgrade_app/2,3
  - downgrade_script/3
  - eval_appup_script/4

  Own Id: OTP-5858

### 1.19 SASL 2.1

#### Improvements and New Features

- A new option {update_paths,Bool} has been added for release_handler:install_release/2. It indicates if all application code paths should be updated (Bool==true), or if only code paths for modified applications should be updated (Bool==false, default).

  release_handler:set_unpacked/2 now returns an error tuple if a specified application directory does not exist.

  *** POTENTIAL INCOMPATIBILITY ***

  Own Id: OTP-5761

### 1.20 SASL 2.0.1

#### Improvements and New Features

- A bug that made it impossible to call rb:show(N) (N being an integer) twice without getting an error has been fixed.

  Own Id: OTP-5287