Ignore:
Timestamp:
Nov 24, 2016, 1:14:11 PM (9 years ago)
Author:
Silvan Scherrer
Message:

Samba Server: update vendor to version 4.4.3

File:
1 edited

Legend:

Unmodified
Added
Removed
  • vendor/current/docs-xml/Samba3-HOWTO/TOSHARG-Bugs.xml

    r414 r988  
    3333
    3434<para>
    35 <indexterm><primary>comp.protocols.smb</primary></indexterm>
    36 <indexterm><primary>newsgroup</primary></indexterm>
    3735<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
     36If you suspect that your
     37problem is not a bug but a configuration problem, it is best to send
    4138it to the Samba mailing list, as there are thousands of other users on
    4239that list who may be able to help you.
     
    261258of the spinning process and type:
    262259<screen>
    263 &rootprompt; gdb /usr/local/samba/sbin/smbd
     260&rootprompt; gdb -p PID
    264261</screen>
    265262<indexterm><primary>spinning process</primary></indexterm>
    266 then <quote>attach `pid'</quote> (of the spinning process), then type <quote>bt</quote> to
     263then type <quote>bt full</quote> to
    267264get a backtrace to see where the smbd is in the call path.
    268265</para>
Note: See TracChangeset for help on using the changeset viewer.