aboutsummaryrefslogtreecommitdiffstats
path: root/lib/sasl/doc/src/sasl_intro.xml
blob: f74a7c1db8cceb13d249d57d973565ef79bce189 (plain) (blame)
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
<?xml version="1.0" encoding="utf-8" ?>
<!DOCTYPE chapter SYSTEM "chapter.dtd">

<chapter>
  <header>
    <copyright>
      <year>1997</year><year>2016</year>
      <holder>Ericsson AB. All Rights Reserved.</holder>
    </copyright>
    <legalnotice>
      Licensed under the Apache License, Version 2.0 (the "License");
      you may not use this file except in compliance with the License.
      You may obtain a copy of the License at
 
          http://www.apache.org/licenses/LICENSE-2.0

      Unless required by applicable law or agreed to in writing, software
      distributed under the License is distributed on an "AS IS" BASIS,
      WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
      See the License for the specific language governing permissions and
      limitations under the License.
    
    </legalnotice>

    <title>Introduction</title>
    <prepared></prepared>
    <docno></docno>
    <date></date>
    <rev></rev>
    <file>sasl_intro.xml</file>
  </header>

  <section>
    <title>Scope</title>
    <p>The SASL application provides support for:</p>
    <list type="bulleted">
      <item>Error logging</item>
      <item>Alarm handling</item>
      <item>Release handling</item>
      <item>Report browsing</item>
    </list>
    <p>Section
      <seealso marker="error_logging">SASL Error Logging</seealso> 
      describes the error
      handler that produces the supervisor, progress, and crash
      reports, which can be written to screen or to a specified file.
      It also describes the Report Browser (RB).</p>
    <p>The sections about release structure and release handling have
      been moved to section
      <seealso marker="doc/design_principles:users_guide">OTP Design Principles</seealso>
      in <em>System Documentation</em>.</p>
  </section>

  <section>
    <title>Prerequisites</title>
    <p>It is assumed that the reader is familiar with the Erlang
      programming language.</p>
  </section>

</chapter>