| 1 | <?xml version="1.0" encoding="UTF-8"?>
|
|---|
| 2 | <!DOCTYPE html
|
|---|
| 3 | PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
|
|---|
| 4 | <html xml:lang="en-us" lang="en-us">
|
|---|
| 5 | <head>
|
|---|
| 6 | <meta http-equiv="Content-Type" content="text/html; charset=utf-8"/>
|
|---|
| 7 | <meta name="copyright" content="(C) Copyright 2005"/>
|
|---|
| 8 | <meta name="DC.rights.owner" content="(C) Copyright 2005"/>
|
|---|
| 9 | <meta name="DC.Type" content="concept"/>
|
|---|
| 10 | <meta name="DC.Title" content="Log files"/>
|
|---|
| 11 | <meta name="abstract" content="When you run the DITA-OT, key information is logged on the screen. This information also is written to a log file. If you encounter a problem, you can analyze this information to determine the source of the problem and then take action to resolve it."/>
|
|---|
| 12 | <meta name="description" content="When you run the DITA-OT, key information is logged on the screen. This information also is written to a log file. If you encounter a problem, you can analyze this information to determine the source of the problem and then take action to resolve it."/>
|
|---|
| 13 | <meta name="DC.Relation" scheme="URI" content="../readme/troubleshooting-overview.html"/>
|
|---|
| 14 | <meta name="DC.Format" content="XHTML"/>
|
|---|
| 15 | <meta name="DC.Identifier" content="loghandling"/>
|
|---|
| 16 | <meta name="DC.Language" content="en-us"/>
|
|---|
| 17 | <link rel="stylesheet" type="text/css" href="../commonltr.css"/>
|
|---|
| 18 | <link rel="stylesheet" type="text/css" href="../dita-ot-doc.css"/>
|
|---|
| 19 | <title>Log files</title>
|
|---|
| 20 | </head>
|
|---|
| 21 | <body id="loghandling">
|
|---|
| 22 |
|
|---|
| 23 |
|
|---|
| 24 | <h1 class="title topictitle1">Log files</h1>
|
|---|
| 25 |
|
|---|
| 26 |
|
|---|
| 27 | <div class="body conbody"><p class="shortdesc">When you run the DITA-OT, key information is logged on the screen. This information
|
|---|
| 28 | also is written to a log file. If you encounter a problem, you can analyze this information to
|
|---|
| 29 | determine the source of the problem and then take action to resolve it.</p>
|
|---|
| 30 |
|
|---|
| 31 | <div class="p">The logging behavior varies depending on whether you use the DITA-OT command-line tool or Ant
|
|---|
| 32 | to invoke a toolkit build.<dl class="dl">
|
|---|
| 33 |
|
|---|
| 34 | <dt class="dt dlterm">Ant</dt>
|
|---|
| 35 |
|
|---|
| 36 | <dd class="dd">By default, status information is written to the screen. If you issue the
|
|---|
| 37 | <span class="keyword parmname">-l</span> parameter, the build runs silently and the information is
|
|---|
| 38 | written to a log file with the name and location that you specified. (You also can use
|
|---|
| 39 | other Ant loggers; see the Ant documentation for more information.)</dd>
|
|---|
| 40 |
|
|---|
| 41 |
|
|---|
| 42 |
|
|---|
| 43 | <dt class="dt dlterm">Command-line tool</dt>
|
|---|
| 44 |
|
|---|
| 45 | <dd class="dd">Status information is written to the screen and the log file. The log file name
|
|---|
| 46 | contains the input file name and transformation type; by default, it is located in the
|
|---|
| 47 | output directory. If you issue the <span class="keyword parmname">/logdir</span> parameter, you can
|
|---|
| 48 | specify a different location for where the log file is written.</dd>
|
|---|
| 49 |
|
|---|
| 50 |
|
|---|
| 51 | </dl>
|
|---|
| 52 | </div>
|
|---|
| 53 |
|
|---|
| 54 |
|
|---|
| 55 |
|
|---|
| 56 |
|
|---|
| 57 | </div>
|
|---|
| 58 |
|
|---|
| 59 | <div class="related-links">
|
|---|
| 60 | <div class="familylinks">
|
|---|
| 61 | <div class="parentlink"><strong>Parent topic:</strong> <a class="link" href="../readme/troubleshooting-overview.html" title="This section contains information about problems that you might encounter and how to resolve them.">Error messages and troubleshooting</a></div>
|
|---|
| 62 | </div>
|
|---|
| 63 | </div>
|
|---|
| 64 |
|
|---|
| 65 | </body>
|
|---|
| 66 | </html>
|
|---|
