From c26bfa21735d9b9d68bf480a52c478f97e986c25 Mon Sep 17 00:00:00 2001 From: John Terpstra Date: Tue, 28 Jun 2005 21:41:48 +0000 Subject: [PATCH] Update. (This used to be commit 04a1961b214a944bb6d489bfa335bf220b708939) --- docs/Samba3-HOWTO/TOSHARG-Bugs.xml | 58 ++++++++++++++++++++++---------------- 1 file changed, 34 insertions(+), 24 deletions(-) diff --git a/docs/Samba3-HOWTO/TOSHARG-Bugs.xml b/docs/Samba3-HOWTO/TOSHARG-Bugs.xml index 1395d8893bc..0ef2c5cc76b 100644 --- a/docs/Samba3-HOWTO/TOSHARG-Bugs.xml +++ b/docs/Samba3-HOWTO/TOSHARG-Bugs.xml @@ -14,11 +14,12 @@ Introduction -Please report bugs using Samba's -Bugzilla facilities and -take the time to read this file before you submit a bug -report. Also, check to see if it has changed between releases, as we -may be changing the bug reporting mechanism at some point. + +Bugzilla +bug reports +Please report bugs using Samba's Bugzilla facilities and take +the time to read this file before you submit a bug report. Also, check to see if it has changed between +releases, as we may be changing the bug reporting mechanism at some point. @@ -31,6 +32,9 @@ us fix it fast. +comp.protocols.smb +newsgroup +configuration problem If you post the bug to the comp.protocols.smb newsgroup or the mailing list, do not assume that we will read it. If you suspect that your problem is not a bug but a configuration problem, it is better to send @@ -80,40 +84,37 @@ detail but may use too much disk space. +debug level +log level To set the debug level, use the in your &smb.conf;. 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, add the following lines to your main &smb.conf; file: - + 10 /usr/local/samba/lib/log.%m /usr/local/samba/lib/smb.conf.%m - + and create a file /usr/local/samba/lib/smb.conf.machine where -machine is the name of the client you wish to debug. In that file -put any &smb.conf; commands you want; for example, - may be useful. This also allows you to -experiment with different security systems, protocol levels, and so on, on just -one machine. +machine is the name of the client you wish to debug. In that file put any +&smb.conf; commands you want; for example, may be useful. This also allows +you to experiment with different security systems, protocol levels, and so on, on just one machine. -The &smb.conf; entry -is synonymous with the parameter that has -been used in older versions of Samba and is being retained for backward +The &smb.conf; entry is synonymous with the parameter that has been used in older versions of Samba and is being retained for backward compatibility of &smb.conf; files. -As the value is increased, you will record -a significantly greater 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 +As the value is increased, you will record a significantly greater 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 large volume of log data. @@ -121,6 +122,10 @@ prepared for a large volume of log data. Debugging-Specific Operations +debugging +logging +functional components +cluttering Samba-3.x permits debugging (logging) of specific functional components without unnecessarily cluttering the log files with detailed logs for all operations. An example configuration to achieve this is shown in: @@ -196,14 +201,14 @@ files. This file is the most useful tool for tracking down the bug. To use it, you do this: gdb debug - - - &prompt;gdb smbd core + +dbx +stack trace adding appropriate paths to smbd and core so gdb can find them. If you do not have gdb, try dbx. Then within the debugger, use the command where to give a stack trace of where the @@ -211,6 +216,7 @@ problem occurred. Include this in your report. +disass If you know any assembly language, do a disass of the routine where the problem occurred (if it's in a library routine, then disassemble the routine that called it) and try to work out exactly @@ -224,6 +230,9 @@ useful. Attaching to a Running Process +PID +gdb +smbstatus 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 @@ -251,8 +260,9 @@ to catch any panics. If smbd seems to be frozen, look for any processes. If it is not, and appears to be spinning, find the PID of the spinning process and type: -gdb /usr/local/samba/sbin/smbd +&rootprompt; gdb /usr/local/samba/sbin/smbd +spinning process then attach `pid' (of the spinning process), then type bt to get a backtrace to see where the smbd is in the call path. -- 2.11.4.GIT