From a84f1e7535b64dcfb1f274097cf947d0ad6fd1ec Mon Sep 17 00:00:00 2001 From: Gerald Carter Date: Thu, 16 Jan 2003 02:21:51 +0000 Subject: regenerate docs (This used to be commit 2215dc37e26bec17eb971e7b54818622a9bb5b97) --- docs/htmldocs/bugreport.html | 31 +++++++++---------------------- 1 file changed, 9 insertions(+), 22 deletions(-) (limited to 'docs/htmldocs/bugreport.html') diff --git a/docs/htmldocs/bugreport.html b/docs/htmldocs/bugreport.html index 9e21f48556..fcc4b7e91a 100644 --- a/docs/htmldocs/bugreport.html +++ b/docs/htmldocs/bugreport.html @@ -5,7 +5,8 @@ >Reporting Bugs

Chapter 26. Reporting Bugs

Chapter 25. Reporting Bugs

26.1. Introduction

25.1. Introduction

The email address for bug reports for stable releases is

26.2. General info

25.2. General info

Before submitting a bug report check your config for silly errors. Look in your log files for obvious messages that tell you that @@ -150,9 +145,7 @@ CLASS="SECT1" >

26.3. Debug levels

25.3. Debug levels

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 @@ -220,9 +213,7 @@ CLASS="SECT1" >

26.4. Internal errors

25.4. Internal errors

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 @@ -264,9 +255,7 @@ CLASS="SECT1" >

26.5. Attaching to a running process

25.5. Attaching to a running process

Unfortunately some unixes (in particular some recent linux kernels) refuse to dump a core file if the task has changed uid (which smbd @@ -281,9 +270,7 @@ CLASS="SECT1" >

26.6. Patches

25.6. Patches

The best sort of bug report is one that includes a fix! If you send us patches please use