1
0
mirror of https://github.com/samba-team/samba.git synced 2025-03-09 08:58:35 +03:00

docs: Clarify TOSHARG-Bugs for 2012

This commit is contained in:
Andrew Bartlett 2012-09-14 23:13:33 -07:00
parent 27359acf59
commit 6bc8616635

View File

@ -32,12 +32,9 @@ us fix it fast.
</para>
<para>
<indexterm><primary>comp.protocols.smb</primary></indexterm>
<indexterm><primary>newsgroup</primary></indexterm>
<indexterm><primary>configuration problem</primary></indexterm>
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
If you suspect that your
problem is not a bug but a configuration problem, it is best to send
it to the Samba mailing list, as there are thousands of other users on
that list who may be able to help you.
</para>
@ -260,10 +257,10 @@ to catch any panics. If <command>smbd</command> 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:
<screen>
&rootprompt; gdb /usr/local/samba/sbin/smbd
&rootprompt; gdb -p PID
</screen>
<indexterm><primary>spinning process</primary></indexterm>
then <quote>attach `pid'</quote> (of the spinning process), then type <quote>bt</quote> to
then type <quote>bt full</quote> to
get a backtrace to see where the smbd is in the call path.
</para>