Changeset 988 for vendor/current/docs-xml/Samba3-HOWTO/TOSHARG-Bugs.xml
- Timestamp:
- Nov 24, 2016, 1:14:11 PM (9 years ago)
- File:
-
- 1 edited
Legend:
- Unmodified
- Added
- Removed
-
vendor/current/docs-xml/Samba3-HOWTO/TOSHARG-Bugs.xml
r414 r988 33 33 34 34 <para> 35 <indexterm><primary>comp.protocols.smb</primary></indexterm>36 <indexterm><primary>newsgroup</primary></indexterm>37 35 <indexterm><primary>configuration problem</primary></indexterm> 38 If you post the bug to the comp.protocols.smb 39 newsgroup or the mailing list, do not assume that we will read it. If you suspect that your 40 problem is not a bug but a configuration problem, it is better to send 36 If you suspect that your 37 problem is not a bug but a configuration problem, it is best to send 41 38 it to the Samba mailing list, as there are thousands of other users on 42 39 that list who may be able to help you. … … 261 258 of the spinning process and type: 262 259 <screen> 263 &rootprompt; gdb /usr/local/samba/sbin/smbd260 &rootprompt; gdb -p PID 264 261 </screen> 265 262 <indexterm><primary>spinning process</primary></indexterm> 266 then <quote>attach `pid'</quote> (of the spinning process), then type <quote>bt</quote> to263 then type <quote>bt full</quote> to 267 264 get a backtrace to see where the smbd is in the call path. 268 265 </para>
Note:
See TracChangeset
for help on using the changeset viewer.
