- Regenerate docs

- Fix db2latex (it depended on the $Id$ tags) - Fix CUPS-Printing syntax - Update instructions in docbook.txt (This used to be commit 8d7c96a4e267c5546518d097edbe03e27b1ad073)
author: Jelmer Vernooij <jelmer@samba.org> 2003-06-06 20:07:16 +0000
committer: Jelmer Vernooij <jelmer@samba.org> 2003-06-06 20:07:16 +0000
commit: f7e07eafc88128a556efbc94a9b062fd48ad91f4 (patch)
tree: eca1673bc2ad9c752869b4f0d99abee35c31acf1 /docs/htmldocs/bugreport.html
parent: bea0cf2c7930b01035109c201d57e43cd29a0591 (diff)
download: samba-f7e07eafc88128a556efbc94a9b062fd48ad91f4.tar.gz
samba-f7e07eafc88128a556efbc94a9b062fd48ad91f4.tar.bz2
samba-f7e07eafc88128a556efbc94a9b062fd48ad91f4.zip
1 files changed, 89 insertions, 322 deletions
diff --git a/docs/htmldocs/bugreport.html b/docs/htmldocs/bugreport.html
index fcc4b7e91a..01b88729ed 100644
--- a/docs/htmldocs/bugreport.html
+++ b/docs/htmldocs/bugreport.html
@@ -1,352 +1,119 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
-<HTML
-><HEAD
-><TITLE
->Reporting Bugs</TITLE
-><META
-NAME="GENERATOR"
-CONTENT="Modular DocBook HTML Stylesheet Version 1.76b+
-"><LINK
-REL="HOME"
-TITLE="SAMBA Project Documentation"
-HREF="samba-howto-collection.html"><LINK
-REL="UP"
-TITLE="Appendixes"
-HREF="appendixes.html"><LINK
-REL="PREVIOUS"
-TITLE="Samba and other CIFS clients"
-HREF="other-clients.html"><LINK
-REL="NEXT"
-TITLE="Diagnosing your samba server"
-HREF="diagnosis.html"></HEAD
-><BODY
-CLASS="CHAPTER"
-BGCOLOR="#FFFFFF"
-TEXT="#000000"
-LINK="#0000FF"
-VLINK="#840084"
-ALINK="#0000FF"
-><DIV
-CLASS="NAVHEADER"
-><TABLE
-SUMMARY="Header navigation table"
-WIDTH="100%"
-BORDER="0"
-CELLPADDING="0"
-CELLSPACING="0"
-><TR
-><TH
-COLSPAN="3"
-ALIGN="center"
->SAMBA Project Documentation</TH
-></TR
-><TR
-><TD
-WIDTH="10%"
-ALIGN="left"
-VALIGN="bottom"
-><A
-HREF="other-clients.html"
-ACCESSKEY="P"
->Prev</A
-></TD
-><TD
-WIDTH="80%"
-ALIGN="center"
-VALIGN="bottom"
-></TD
-><TD
-WIDTH="10%"
-ALIGN="right"
-VALIGN="bottom"
-><A
-HREF="diagnosis.html"
-ACCESSKEY="N"
->Next</A
-></TD
-></TR
-></TABLE
-><HR
-ALIGN="LEFT"
-WIDTH="100%"></DIV
-><DIV
-CLASS="CHAPTER"
-><H1
-><A
-NAME="BUGREPORT">Chapter 25. Reporting Bugs</H1
-><DIV
-CLASS="SECT1"
-><H1
-CLASS="SECT1"
-><A
-NAME="AEN3309">25.1. Introduction</H1
-><P
->The email address for bug reports for stable releases is <A
-HREF="samba@samba.org"
-TARGET="_top"
->samba@samba.org</A
->. 
-Bug reports for alpha releases should go to <A
-HREF="mailto:samba-technical@samba.org"
-TARGET="_top"
->samba-technical@samba.org</A
->.</P
-><P
->Please take the time to read this file before you submit a bug
+<html><head><meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"><title>Chapter 35. Reporting Bugs</title><link rel="stylesheet" href="samba.css" type="text/css"><meta name="generator" content="DocBook XSL Stylesheets V1.60.1"><link rel="home" href="index.html" title="SAMBA Project Documentation"><link rel="up" href="troubleshooting.html" title="Part V. Troubleshooting"><link rel="previous" href="problems.html" title="Chapter 34. Analysing and solving samba problems"><link rel="next" href="Appendixes.html" title="Part VI. Appendixes"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="navheader"><table width="100%" summary="Navigation header"><tr><th colspan="3" align="center">Chapter 35. Reporting Bugs</th></tr><tr><td width="20%" align="left"><a accesskey="p" href="problems.html">Prev</a> </td><th width="60%" align="center">Part V. Troubleshooting</th><td width="20%" align="right"> <a accesskey="n" href="Appendixes.html">Next</a></td></tr></table><hr></div><div class="chapter" lang="en"><div class="titlepage"><div><div><h2 class="title"><a name="bugreport"></a>Chapter 35. Reporting Bugs</h2></div><div><div class="author"><h3 class="author"><span class="firstname">Jelmer</span> <span class="othername">R.</span> <span class="surname">Vernooij</span></h3><div class="affiliation"><span class="orgname">The Samba Team<br></span><div class="address"><p><tt class="email">&lt;<a href="mailto:jelmer@samba.org">jelmer@samba.org</a>&gt;</tt></p></div></div></div></div><div><div class="author"><h3 class="author"><span class="surname">Someone; Tridge or Karl Auer perhaps?</span></h3></div></div><div><p class="pubdate"> 27 June 1997 </p></div></div><div></div></div><div class="toc"><p><b>Table of Contents</b></p><dl><dt><a href="bugreport.html#id3011690">Introduction</a></dt><dt><a href="bugreport.html#id3011912">General info</a></dt><dt><a href="bugreport.html#id3011949">Debug levels</a></dt><dt><a href="bugreport.html#id3012091">Internal errors</a></dt><dt><a href="bugreport.html#id3012199">Attaching to a running process</a></dt><dt><a href="bugreport.html#id3012246">Patches</a></dt></dl></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id3011690"></a>Introduction</h2></div></div><div></div></div><p>Please report bugs using
+	<a href="https://bugzilla.samba.org/" target="_top">bugzilla</a>.</p><p>
+Please take the time to read this file before you submit a bug
 report. Also, please see if it has changed between releases, as we
-may be changing the bug reporting mechanism at some time.</P
-><P
->Please also do as much as you can yourself to help track down the
+may be changing the bug reporting mechanism at some time.
+</p><p>
+Please also do as much as you can yourself to help track down the
 bug. Samba is maintained by a dedicated group of people who volunteer
 their time, skills and efforts. We receive far more mail about it than
 we can possibly answer, so you have a much higher chance of an answer
-and a fix if you send us a "developer friendly" bug report that lets
-us fix it fast. </P
-><P
->Do not assume that if you post the bug to the comp.protocols.smb
+and a fix if you send us a &quot;developer friendly&quot; bug report that lets
+us fix it fast. 
+</p><p>
+Do not assume that if you post the bug to the comp.protocols.smb
 newsgroup or the mailing list that we will read it. If you suspect that your 
 problem is not a bug but a configuration problem then it is better to send 
 it to the Samba mailing list, as there are (at last count) 5000 other users on
-that list that may be able to help you.</P
-><P
->You may also like to look though the recent mailing list archives,
+that list that may be able to help you.
+</p><p>
+You may also like to look though the recent mailing list archives,
 which are conveniently accessible on the Samba web pages
-at <A
-HREF="http://samba.org/samba/"
-TARGET="_top"
->http://samba.org/samba/</A
->.</P
-></DIV
-><DIV
-CLASS="SECT1"
-><H1
-CLASS="SECT1"
-><A
-NAME="AEN3319">25.2. General info</H1
-><P
->Before submitting a bug report check your config for silly
+at <a href="http://samba.org/samba/" target="_top">http://samba.org/samba/</a>.
+</p></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id3011912"></a>General info</h2></div></div><div></div></div><p>
+Before submitting a bug report check your config for silly
 errors. Look in your log files for obvious messages that tell you that
 you've misconfigured something and run testparm to test your config
-file for correct syntax.</P
-><P
->Have you run through the <A
-HREF="Diagnosis.html"
-TARGET="_top"
->diagnosis</A
->? 
-This is very important.</P
-><P
->If you include part of a log file with your bug report then be sure to
+file for correct syntax.
+</p><p>
+Have you run through the <a href="diagnosis.html" title="Chapter 33. The samba checklist">diagnosis</a>? 
+This is very important.
+</p><p>
+If you include part of a log file with your bug report then be sure to
 annotate it with exactly what you were doing on the client at the
-time, and exactly what the results were.</P
-></DIV
-><DIV
-CLASS="SECT1"
-><H1
-CLASS="SECT1"
-><A
-NAME="AEN3325">25.3. Debug levels</H1
-><P
->If the bug has anything to do with Samba behaving incorrectly as a
+time, and exactly what the results were.
+</p></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id3011949"></a>Debug levels</h2></div></div><div></div></div><p>
+If the bug has anything to do with Samba behaving incorrectly as a
 server (like refusing to open a file) then the log files will probably
 be very useful. Depending on the problem a log level of between 3 and
 10 showing the problem may be appropriate. A higher level givesmore
-detail, but may use too much disk space.</P
-><P
->To set the debug level use <B
-CLASS="COMMAND"
->log level =</B
-> in your 
-<TT
-CLASS="FILENAME"
->smb.conf</TT
->. You may also find it useful to set the log 
+detail, but may use too much disk space.
+</p><p>
+To set the debug level use the <i class="parameter"><tt>log level</tt></i> in your 
+<tt class="filename">smb.conf</tt>. You may also find it useful to set the log 
 level higher for just one machine and keep separate logs for each machine. 
-To do this use:</P
-><P
-><PRE
-CLASS="PROGRAMLISTING"
->log level = 10
+To do this use:
+</p><pre class="programlisting">
+log level = 10
 log file = /usr/local/samba/lib/log.%m
-include = /usr/local/samba/lib/smb.conf.%m</PRE
-></P
-><P
->then create a file 
-<TT
-CLASS="FILENAME"
->/usr/local/samba/lib/smb.conf.machine</TT
-> where
-"machine" is the name of the client you wish to debug. In that file
-put any smb.conf commands you want, for example 
-<B
-CLASS="COMMAND"
->log level=</B
-> may be useful. This also allows you to 
+include = /usr/local/samba/lib/smb.conf.%m
+</pre><p>
+then create a file 
+<tt class="filename">/usr/local/samba/lib/smb.conf.<i class="replaceable"><tt>machine</tt></i></tt> where
+<i class="replaceable"><tt>machine</tt></i> is the name of the client you wish to debug. In that file
+put any <tt class="filename">smb.conf</tt> commands you want, for example 
+<i class="parameter"><tt>log level</tt></i> may be useful. This also allows you to 
 experiment with different security systems, protocol levels etc on just 
-one machine.</P
-><P
->The <TT
-CLASS="FILENAME"
->smb.conf</TT
-> entry <B
-CLASS="COMMAND"
->log level =</B
-> 
-is synonymous with the entry <B
-CLASS="COMMAND"
->debuglevel =</B
-> that has been 
-used in older versions of Samba and is being retained for backwards 
-compatibility of smb.conf files.</P
-><P
->As the <B
-CLASS="COMMAND"
->log level =</B
-> value is increased you will record 
+one machine.
+</p><p>
+The <tt class="filename">smb.conf</tt> entry <i class="parameter"><tt>log level</tt></i> 
+is synonymous with the parameter <i class="parameter"><tt>debuglevel</tt></i> that has
+been used in older versions of Samba and is being retained for backwards 
+compatibility of <tt class="filename">smb.conf</tt> files.
+</p><p>
+As the <i class="parameter"><tt>log level</tt></i> value is increased you will record 
 a significantly increasing level of debugging information. For most 
-debugging operations you may not need a setting higher than 3. Nearly 
-all bugs can be tracked at a setting of 10, but be prepared for a VERY 
-large volume of log data.</P
-></DIV
-><DIV
-CLASS="SECT1"
-><H1
-CLASS="SECT1"
-><A
-NAME="AEN3342">25.4. Internal errors</H1
-><P
->If you get a "INTERNAL ERROR" message in your log files it means that
-Samba got an unexpected signal while running. It is probably a
+debugging operations you may not need a setting higher than 
+<tt class="constant">3</tt>. Nearly 
+all bugs can be tracked at a setting of <tt class="constant">10</tt>, but be 
+prepared for a VERY large volume of log data.
+</p></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id3012091"></a>Internal errors</h2></div></div><div></div></div><p>
+If you get a <span class="errorname">INTERNAL ERROR</span> message in your log files 
+it means that Samba got an unexpected signal while running. It is probably a
 segmentation fault and almost certainly means a bug in Samba (unless
-you have faulty hardware or system software)</P
-><P
->If the message came from smbd then it will probably be accompanied by
+you have faulty hardware or system software).
+</p><p>
+If the message came from smbd then it will probably be accompanied by
 a message which details the last SMB message received by smbd. This
 info is often very useful in tracking down the problem so please
-include it in your bug report.</P
-><P
->You should also detail how to reproduce the problem, if
-possible. Please make this reasonably detailed.</P
-><P
->You may also find that a core file appeared in a "corefiles"
+include it in your bug report.
+</p><p>
+You should also detail how to reproduce the problem, if
+possible. Please make this reasonably detailed.
+</p><p>
+You may also find that a core file appeared in a <tt class="filename">corefiles</tt>
 subdirectory of the directory where you keep your samba log
 files. This file is the most useful tool for tracking down the bug. To
-use it you do this:</P
-><P
-><B
-CLASS="COMMAND"
->gdb smbd core</B
-></P
-><P
->adding appropriate paths to smbd and core so gdb can find them. If you
-don't have gdb then try "dbx". Then within the debugger use the
-command "where" to give a stack trace of where the problem
-occurred. Include this in your mail.</P
-><P
->If you known any assembly language then do a "disass" of the routine
+use it you do this:
+</p><pre class="screen">
+	<tt class="prompt">$ </tt><b class="userinput"><tt>gdb smbd core</tt></b>
+</pre><p>
+adding appropriate paths to smbd and core so gdb can find them. If you
+don't have gdb then try <b class="userinput"><tt>dbx</tt></b>. Then within the debugger
+use the command <b class="command">where</b> to give a stack trace of where the
+problem occurred. Include this in your report.
+</p><p>
+If you know any assembly language then do a 
+<b class="command">disass</b> of the routine
 where the problem occurred (if its in a library routine then
 disassemble the routine that called it) and try to work out exactly
 where the problem is by looking at the surrounding code. Even if you
 don't know assembly then incuding this info in the bug report can be
-useful. </P
-></DIV
-><DIV
-CLASS="SECT1"
-><H1
-CLASS="SECT1"
-><A
-NAME="AEN3352">25.5. Attaching to a running process</H1
-><P
->Unfortunately some unixes (in particular some recent linux kernels)
+useful. 
+</p></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id3012199"></a>Attaching to a running process</h2></div></div><div></div></div><p>
+Unfortunately some unixes (in particular some recent linux kernels)
 refuse to dump a core file if the task has changed uid (which smbd
 does often). To debug with this sort of system you could try to attach
-to the running process using "gdb smbd PID" where you get PID from
-smbstatus. Then use "c" to continue and try to cause the core dump
+to the running process using
+<b class="userinput"><tt>gdb smbd <i class="replaceable"><tt>PID</tt></i></tt></b> where you get
+<i class="replaceable"><tt>PID</tt></i> from <span class="application">smbstatus</span>.
+Then use <b class="command">c</b> to continue and try to cause the core dump
 using the client. The debugger should catch the fault and tell you
-where it occurred.</P
-></DIV
-><DIV
-CLASS="SECT1"
-><H1
-CLASS="SECT1"
-><A
-NAME="AEN3355">25.6. Patches</H1
-><P
->The best sort of bug report is one that includes a fix! If you send us
-patches please use <B
-CLASS="COMMAND"
->diff -u</B
-> format if your version of 
-diff supports it, otherwise use <B
-CLASS="COMMAND"
->diff -c4</B
->. Make sure 
-your do the diff against a clean version of the source and let me know 
-exactly what version you used. </P
-></DIV
-></DIV
-><DIV
-CLASS="NAVFOOTER"
-><HR
-ALIGN="LEFT"
-WIDTH="100%"><TABLE
-SUMMARY="Footer navigation table"
-WIDTH="100%"
-BORDER="0"
-CELLPADDING="0"
-CELLSPACING="0"
-><TR
-><TD
-WIDTH="33%"
-ALIGN="left"
-VALIGN="top"
-><A
-HREF="other-clients.html"
-ACCESSKEY="P"
->Prev</A
-></TD
-><TD
-WIDTH="34%"
-ALIGN="center"
-VALIGN="top"
-><A
-HREF="samba-howto-collection.html"
-ACCESSKEY="H"
->Home</A
-></TD
-><TD
-WIDTH="33%"
-ALIGN="right"
-VALIGN="top"
-><A
-HREF="diagnosis.html"
-ACCESSKEY="N"
->Next</A
-></TD
-></TR
-><TR
-><TD
-WIDTH="33%"
-ALIGN="left"
-VALIGN="top"
->Samba and other CIFS clients</TD
-><TD
-WIDTH="34%"
-ALIGN="center"
-VALIGN="top"
-><A
-HREF="appendixes.html"
-ACCESSKEY="U"
->Up</A
-></TD
-><TD
-WIDTH="33%"
-ALIGN="right"
-VALIGN="top"
->Diagnosing your samba server</TD
-></TR
-></TABLE
-></DIV
-></BODY
-></HTML
->
-\ No newline at end of file
+where it occurred.
+</p></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id3012246"></a>Patches</h2></div></div><div></div></div><p>
+The best sort of bug report is one that includes a fix! If you send us
+patches please use <b class="userinput"><tt>diff -u</tt></b> format if your version of 
+diff supports it, otherwise use <b class="userinput"><tt>diff -c4</tt></b>. Make sure 
+you do the diff against a clean version of the source and let me know 
+exactly what version you used. 
+</p></div></div><div class="navfooter"><hr><table width="100%" summary="Navigation footer"><tr><td width="40%" align="left"><a accesskey="p" href="problems.html">Prev</a> </td><td width="20%" align="center"><a accesskey="u" href="troubleshooting.html">Up</a></td><td width="40%" align="right"> <a accesskey="n" href="Appendixes.html">Next</a></td></tr><tr><td width="40%" align="left" valign="top">Chapter 34. Analysing and solving samba problems </td><td width="20%" align="center"><a accesskey="h" href="index.html">Home</a></td><td width="40%" align="right" valign="top"> Part VI. Appendixes</td></tr></table></div></body></html>
author	Jelmer Vernooij <jelmer@samba.org>	2003-06-06 20:07:16 +0000
committer	Jelmer Vernooij <jelmer@samba.org>	2003-06-06 20:07:16 +0000
commit	f7e07eafc88128a556efbc94a9b062fd48ad91f4 (patch)
tree	eca1673bc2ad9c752869b4f0d99abee35c31acf1 /docs/htmldocs/bugreport.html
parent	bea0cf2c7930b01035109c201d57e43cd29a0591 (diff)
download	samba-f7e07eafc88128a556efbc94a9b062fd48ad91f4.tar.gz samba-f7e07eafc88128a556efbc94a9b062fd48ad91f4.tar.bz2 samba-f7e07eafc88128a556efbc94a9b062fd48ad91f4.zip