even easier

[Imported from Trac: page HowToReportABug, version 2]
zooko 2010-06-03 18:11:17 +00:00
parent 0839ea2581
commit 0886b83e04

@ -7,4 +7,6 @@ Either [subscribe to tahoe-dev](http://allmydata.org/cgi-bin/mailman/listinfo/ta
* the version of Tahoe-LAFS that you are using; If unsure, run `tahoe --version` or look at the welcome page on the web user interface. All of the version numbers listed are potentially useful, so just cut and paste them all into your report, or if that is inconvenient for some reason then just tell us the `allmydata-tahoe` version number.
* if the problem happens every time or if it is sporadic; Exactly when the problem does and doesn't manifest itself is usually the best clue for us to start with.
If you don't mind taking an extra few minutes of your time to include the log files, then please include them with your bug report. You can find them in the `logs` subdirectory of the Tahoe-LAFS base directory. The log file named `twistd.log` might be useful, and any log files which are located in the `logs/incidents` subdirectory and which have timestamps around the time of the problem might be useful.
If you don't mind taking an extra few minutes of your time to include the log files, then please include them with your bug report. You can find them in the `logs` subdirectory of the Tahoe-LAFS base directory. The log file named `twistd.log` might be useful, and any log files which are located in the `logs/incidents` subdirectory and which have timestamps around the time of the problem might be useful.
Actually, if you include any incident report log files then the log file will contain the version numbers so you don't need to paste in the version numbers.