Ana Sayfa Keşfet Yardım
Giriş Yap
bn
/
se
2
0
Çatalla 0
Dosyalar Sorunlar 0 Değişiklik İstekleri 0 Wiki
Ağaç: 0b6fc7fd2b
Dallar Biçim İmleri
se
/
SE
/
stuff
/
dita-ot-2.3.3
/
doc
/
user-guide
/
log-files.html

log-files.html 4.7 KB
Geçmiş Ham

123456789101112131415161718192021222324252627282930313233 
  1. <!DOCTYPE html
    2. 

  2.   SYSTEM "about:legacy-compat">
    3. 

  3. <html lang="en-us"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8"><meta charset="UTF-8"><meta name="copyright" content="(C) Copyright 2016"><meta name="DC.rights.owner" content="(C) Copyright 2016"><meta name="DC.Type" content="concept"><meta name="description" content="When you run the DITA-OT, key information is logged on the screen. This information can also be 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."><meta name="DC.Relation" scheme="URI" content="../user-guide/troubleshooting-overview.html"><meta name="DC.Format" content="XHTML"><meta name="DC.Identifier" content="loghandling"><meta name="DC.Language" content="en-US"><link rel="stylesheet" type="text/css" href="../css/commonltr.css"><link rel="stylesheet" type="text/css" href="../css/dita-ot-doc.css"><title>Log files</title></head><body id="loghandling"><header role="banner"><div class="header">
    4. 

  4.   <p>DITA Open Toolkit</p>
    5. 

  5.   <hr>
    6. 

  6. </div></header><nav role="toc"><ul><li><a href="../index.html">DITA Open Toolkit 2.3</a></li><li><a href="../release-notes/index.html">Release Notes</a></li><li><a href="../getting-started/index.html">Getting Started</a></li><li><a href="../user-guide/index.html">User Guide</a><ul><li><a href="../user-guide/transforming-dita-content.html">Publishing DITA content</a></li><li><a href="../user-guide/AvailableTransforms.html">Output formats</a></li><li><a href="../user-guide/DITA_spec-support.html">DITA specification support</a></li><li><a href="../user-guide/DITA-globalization.html">Globalizing DITA content</a></li><li><a href="../user-guide/troubleshooting-overview.html">Troubleshooting</a><ul><li><a href="../user-guide/prerequisite-software.html">Prerequisite software</a></li><li><a href="../user-guide/DITA-messages.html">DITA-OT error messages</a></li><li><a href="../user-guide/other-errors.html">Other error messages</a></li><li class="active"><a href="../user-guide/log-files.html">Log files</a></li><li><a href="../user-guide/dita-command-help.html">Accessing help for the dita command</a></li><li><a href="../user-guide/determining-version-of-ditaot.html">Checking the DITA-OT version</a></li><li><a href="../user-guide/enabling-debug-mode.html">Enabling debug mode</a></li><li><a href="../user-guide/increasing-the-jvm.html">Increasing Java memory allocation</a></li><li><a href="../user-guide/reducing-processing-time.html">Reducing processing time</a></li></ul></li></ul></li><li><a href="../parameters/index.html">Parameter Reference</a></li><li><a href="../dev_ref/index.html">Developer Reference</a></li><li><a href="../user-guide/dita-and-dita-ot-resources.html">DITA Resources</a></li></ul></nav><main role="main"><article role="article" aria-labelledby="ariaid-title1">
    7. 

  7.   <h1 class="title topictitle1" id="ariaid-title1">Log files</h1>
    8. 

  8.   
    9. 

  9.   <div class="body conbody"><p class="shortdesc">When you run the DITA-OT, key information is logged on the screen. This information can also be written to
    10. 

  10.     a log file. If you encounter a problem, you can analyze this information to determine the source of the problem and
    11. 

  11.     then take action to resolve it.</p>
    12. 

  12.     <div class="p">The logging behavior varies depending on whether you use the <span class="keyword cmdname">dita</span> command, DITA-OT
    13. 

  13.       command-line tool, or Ant to invoke a toolkit build.<dl class="dl">
    14. 

  14.         
    15. 

  15.           <dt class="dt dlterm"><span class="keyword cmdname">dita</span> command</dt>
    16. 

  16.           <dd class="dd">By default, only warning and error messages are written to the screen. If you use the
    17. 

  17.               <span class="keyword parmname">-v</span> option, logging will be more verbose and informative messages are also written
    18. 

  18.             out. The <span class="keyword parmname">-l</span> option can be used to write the log messages into a file.</dd>
    19. 

  19.         
    20. 

  20.         
    21. 

  21.           <dt class="dt dlterm">Ant</dt>
    22. 

  22.           <dd class="dd">By default, status information is written to the screen. If you issue the <span class="keyword parmname">-l</span>
    23. 

  23.             parameter, the build runs silently and the information is written to a log file with the name and location
    24. 

  24.             that you specified. (You also can use other Ant loggers; see the Ant documentation for more
    25. 

  25.             information.)</dd>
    26. 

  26.         
    27. 

  27.         
    28. 

  28.       </dl></div>
    29. 

  29.     
    30. 

  30.     
    31. 

  31.     
    32. 

  32.   </div>
    33. 

  33. <nav role="navigation" class="related-links"><div class="familylinks"><div class="parentlink"><strong>Parent topic:</strong> <a class="link" href="../user-guide/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></div></nav></article></main></body></html>
    34.