From 20967627378194121bc48bf387838b8bd7682478 Mon Sep 17 00:00:00 2001 From: Jelmer Vernooij Date: Tue, 18 Mar 2003 16:48:14 +0000 Subject: Regenerate (This used to be commit 25db62e3101dbcae8e9daee3cb16430297afa223) --- docs/htmldocs/bugreport.html | 54 ++++++++++++++++++++++---------------------- 1 file changed, 27 insertions(+), 27 deletions(-) (limited to 'docs/htmldocs/bugreport.html') diff --git a/docs/htmldocs/bugreport.html b/docs/htmldocs/bugreport.html index 813d0055cc..cc4fc83df6 100644 --- a/docs/htmldocs/bugreport.html +++ b/docs/htmldocs/bugreport.html @@ -5,7 +5,7 @@ >Reporting BugsPrevChapter 23. Reporting BugsChapter 24. Reporting Bugs

23.1. Introduction

24.1. Introduction

The email address for bug reports for stable releases is

23.2. General info

24.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 +150,9 @@ CLASS="SECT1" >

23.3. Debug levels

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

23.4. Internal errors

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

23.5. Attaching to a running process

24.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 +281,9 @@ CLASS="SECT1" >

23.6. Patches

24.6. Patches

The best sort of bug report is one that includes a fix! If you send us patches please use PrevSamba and other CIFS clientsHow to compile SAMBADiagnosing your samba serverThe samba checklist