aboutsummaryrefslogtreecommitdiffstats
path: root/lib/sasl/src
AgeCommit message (Collapse)Author
2010-08-20sasl: Patch 1116Björn Gustavsson
OTP-8619 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.
2010-08-20sasl: Patch 1109Björn Gustavsson
OTP-8506 <p>Use an infinity timeout in all calls to <c>gen_server:call()</c> in the <c>sasl</c> application.</p>
2010-02-17Merge branch 'ks/cleanups' into ccase/r13b04_devErlang/OTP
* ks/cleanups: percept: Clean up as suggested by tidier percept: Modernize types and specs parsetools: Don't use 'try...of' when 'try' will do parsetools: Use %% for comments at the beginning of a line parsetools: Replace lists:keysearch/3 with lists:keyfind/3 parsetools: Modernize types and specs parsetools: Replace TABs with spaces runtime_tools: Modernize specs sasl: Eliminate tuple used as fun sasl: Add missing modules to app file asn1: Clean up as suggested by tidier os_mon: Modernize types and specs wx: Clean up as suggested by tidier OTP-8455 ks/cleanups
2010-02-16sasl: Eliminate tuple used as funKostis Sagonas
2010-02-16sasl: Add missing modules to app fileKostis Sagonas
2010-02-16Merge branch 'jn/sasl-format_report' into ccase/r13b04_devErlang/OTP
* jn/sasl-format_report: Added sasl_report:format_report/3 to return a string rather than send an io OTP-8445 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.)
2010-02-16Merge branch 'va/rb-improvements' into ccase/r13b04_devErlang/OTP
* va/rb-improvements: New rb:filter/2 to filter reports by date New rb:filter/1 function to ease report filtering Modify rb:grep/1 to grep reports using the re module Fix minor typo in read_report/1 OTP-8443 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.)
2010-02-14Added sasl_report:format_report/3 to return a string rather than send an ioJay Nelson
sasl_report:write_report/3 calls io:format to output the report message, but does not provide an option to generate a formatted string rather than sending the message. sasl_report:format_report/3 is added to allow the replacement of sasl_report with a different handler but still generate reports in the same format. It returns the string generated by io_lib:format. sasl_report:write_report/3 retains its original behavior. This patch was submitted in 2008 (see http://www.erlang.org/cgi-bin/ezmlm-cgi/4/35061) but was never incorporated into the source.
2010-02-14New rb:filter/2 to filter reports by dateAlvaro Videla
The function filter/2 expects a second parameter Dates that can be used to return reports that occurred between the provided dates. Usage: Dec22 = {{2009,12,22},{0,0,0}}. Dec24 = {{2009,12,24},{0,0,0}}. rb:filter(Filters, {Dec22, from}). %will return reports that occurred from Dec22. rb:filter(Filters, {Dec22, to}). %will return reports that occurred before Dec22. rb:filter(Filters, {Dec22, Dec24}). %will return reports that occurred between Dec22 % and Dec24
2010-02-14New rb:filter/1 function to ease report filteringAlvaro Videla
Currently in the rb module the only way to filter reports is by using the grep/1 or re/1 functions that use Regular Expressions. This new function allow us to specify detailed filters that will match against our reports. Since the reports are proplists the filters are tuples of the form {Key, Value}. If the report contains that tuple, it will be displayed. Usage: 1> rb:filter([{"foo", "bar"}, {"abc", "value"}]). 2> rb:filter([{"foo", "bar", no}]). % excludes reports containing {"foo", "bar"} 3> rb:filter([{"foo", RegExp, re}]). % the report must contain an element with Key = "foo" % and Value must match RegExp
2010-02-14Modify rb:grep/1 to grep reports using the re moduleAlvaro Videla
2010-02-14Fix minor typo in read_report/1Alvaro Videla
2009-11-20The R13B03 release.OTP_R13B03Erlang/OTP