sin/samba-mirror
1
0
Fork 0
mirror of https://github.com/samba-team/samba.git synced 2025-01-08 21:18:16 +03:00
Code

Added reference to DIAGNOSIS.txt. Deleted the claim that tridge reads all

Browse Source 
postings to mailing list. Removed arvidsjaur, other small stuff.
   Dan
(This used to be commit af463f82c5)
This commit is contained in:
Samba Release Account 1996-05-23 23:50:59 +00:00
parent b64f106c26
commit 09050330b0
1 changed files with 5 additions and 8 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

13
docs/textdocs/BUGS.txt
View File

@ -2,10 +2,6 @@ This file describes how to report Samba bugs.
>> The email address for bug reports is samba-bugs@anu.edu.au << >> The email address for bug reports is samba-bugs@anu.edu.au <<
(NOTE: This mail may not be in place yet. If you have troubles with it
then use samba-bugs@arvidsjaur.anu.edu.au)
Please take the time to read this file before you submit a bug Please take the time to read this file before you submit a bug
report. Also, please see if it has changed between releases, as I report. Also, please see if it has changed between releases, as I
may be changing the bug reporting mechanism sometime soon. may be changing the bug reporting mechanism sometime soon.
@ -17,10 +13,9 @@ of an answer and a fix if you send me a "developer friendly" bug
report that lets me fix it fast. report that lets me fix it fast.
Do not assume that if you post the bug to the comp.protocols.smb Do not assume that if you post the bug to the comp.protocols.smb
newsgroup that I will read it. I do read all postings to the samba newsgroup or the mailing list that I will read it. If you suspect that your
mailing list (see the README). If you suspect that your problem is not problem is not a bug but a configuration problem then it is better to send
a bug but a configuration problem then it is better to send it to the it to the Samba mailing list, as there are (at last count) 1900 other users on
Samba mailing list, as there are (at last count) 1900 other users on
that list that may be able to help you. that list that may be able to help you.
You may also like to look though the recent mailing list archives, You may also like to look though the recent mailing list archives,
@ -36,6 +31,8 @@ errors. Look in your log files for obvious messages that tell you that
you've misconfigured something and run testparm to test your config you've misconfigured something and run testparm to test your config
file for correct syntax. file for correct syntax.
Have you run through DIAGNOSIS.txt? This is very important.
If you include part of a log file with your bug report then be sure to If you include part of a log file with your bug report then be sure to
annotate it with exactly what you were doing on the client at the annotate it with exactly what you were doing on the client at the
time, and exactly what the results were. time, and exactly what the results were.