1
0

node3.html 7.5 KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104105106107108109110111112113114115116117118119120121122123124125126127128129130131132133134135136137138139140141142143144145146147148149150151152153154155156157158159160161162163164165166167168169170171172173174175176177178179180181182183184185186187188189190191192193194195196197198199200201202203204205206207208209210211212
  1. <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
  2. <!--Converted with LaTeX2HTML 2002-2-1 (1.70)
  3. original version by: Nikos Drakos, CBLU, University of Leeds
  4. * revised and updated by: Marcus Hennecke, Ross Moore, Herb Swan
  5. * with significant contributions from:
  6. Jens Lippmann, Marek Rouchal, Martin Wilck and others -->
  7. <HTML>
  8. <HEAD>
  9. <TITLE>2 Bugs, Feature Requests, and Patches</TITLE>
  10. <META NAME="description" CONTENT="2 Bugs, Feature Requests, and Patches">
  11. <META NAME="keywords" CONTENT="FAQ">
  12. <META NAME="resource-type" CONTENT="document">
  13. <META NAME="distribution" CONTENT="global">
  14. <META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1">
  15. <META NAME="Generator" CONTENT="LaTeX2HTML v2002-2-1">
  16. <META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
  17. <LINK REL="STYLESHEET" HREF="FAQ.css">
  18. <LINK REL="next" HREF="node4.html">
  19. <LINK REL="previous" HREF="node2.html">
  20. <LINK REL="up" HREF="FAQ.html">
  21. <LINK REL="next" HREF="node4.html">
  22. </HEAD>
  23. <BODY >
  24. <DIV CLASS="navigation"><!--Navigation Panel-->
  25. <A NAME="tex2html156"
  26. HREF="node4.html">
  27. <IMG WIDTH="37" HEIGHT="24" ALIGN="BOTTOM" BORDER="0" ALT="next" SRC="next.png"></A>
  28. <A NAME="tex2html152"
  29. HREF="FAQ.html">
  30. <IMG WIDTH="26" HEIGHT="24" ALIGN="BOTTOM" BORDER="0" ALT="up" SRC="up.png"></A>
  31. <A NAME="tex2html146"
  32. HREF="node2.html">
  33. <IMG WIDTH="63" HEIGHT="24" ALIGN="BOTTOM" BORDER="0" ALT="previous" SRC="prev.png"></A>
  34. <A NAME="tex2html154"
  35. HREF="node1.html">
  36. <IMG WIDTH="65" HEIGHT="24" ALIGN="BOTTOM" BORDER="0" ALT="contents" SRC="contents.png"></A>
  37. <BR>
  38. <B> Next:</B> <A NAME="tex2html157"
  39. HREF="node4.html">3 Understanding tcpprep</A>
  40. <B> Up:</B> <A NAME="tex2html153"
  41. HREF="FAQ.html">Tcpreplay 3.x FAQ</A>
  42. <B> Previous:</B> <A NAME="tex2html147"
  43. HREF="node2.html">1 General Info</A>
  44. &nbsp; <B> <A NAME="tex2html155"
  45. HREF="node1.html">Contents</A></B>
  46. <BR>
  47. <BR></DIV>
  48. <!--End of Navigation Panel-->
  49. <!--Table of Child-Links-->
  50. <A NAME="CHILD_LINKS"><STRONG>Subsections</STRONG></A>
  51. <UL CLASS="ChildLinks">
  52. <LI><A NAME="tex2html158"
  53. HREF="node3.html#SECTION00031000000000000000"><SPAN CLASS="arabic">2</SPAN>.<SPAN CLASS="arabic">1</SPAN> Where can I get help, report bugs or contact the developers?</A>
  54. <LI><A NAME="tex2html159"
  55. HREF="node3.html#SECTION00032000000000000000"><SPAN CLASS="arabic">2</SPAN>.<SPAN CLASS="arabic">2</SPAN> What information should I provide when I report a bug?</A>
  56. <LI><A NAME="tex2html160"
  57. HREF="node3.html#SECTION00033000000000000000"><SPAN CLASS="arabic">2</SPAN>.<SPAN CLASS="arabic">3</SPAN> I have a feature request, what should I do?</A>
  58. <LI><A NAME="tex2html161"
  59. HREF="node3.html#SECTION00034000000000000000"><SPAN CLASS="arabic">2</SPAN>.<SPAN CLASS="arabic">4</SPAN> I've written a patch for tcpreplay, how can I submit it?</A>
  60. <LI><A NAME="tex2html162"
  61. HREF="node3.html#SECTION00035000000000000000"><SPAN CLASS="arabic">2</SPAN>.<SPAN CLASS="arabic">5</SPAN> Patch requirements</A>
  62. </UL>
  63. <!--End of Table of Child-Links-->
  64. <HR>
  65. <H1><A NAME="SECTION00030000000000000000">
  66. <SPAN CLASS="arabic">2</SPAN> Bugs, Feature Requests, and Patches</A>
  67. </H1>
  68. <P>
  69. <H2><A NAME="SECTION00031000000000000000">
  70. <SPAN CLASS="arabic">2</SPAN>.<SPAN CLASS="arabic">1</SPAN> Where can I get help, report bugs or contact the developers?</A>
  71. </H2>
  72. <P>
  73. The best place to get help or report a bug is the Tcpreplay-Users
  74. mailing list:
  75. <BR>
  76. http://lists.sourceforge.net/lists/listinfo/tcpreplay-users
  77. <P>
  78. <H2><A NAME="SECTION00032000000000000000">
  79. <SPAN CLASS="arabic">2</SPAN>.<SPAN CLASS="arabic">2</SPAN> What information should I provide when I report a bug?</A>
  80. </H2>
  81. <P>
  82. One of the most frustrating things for any developer trying to help
  83. a user with a problem is not enough information. Please be sure to
  84. include <SPAN CLASS="textit">at minimum</SPAN> the following information, however any additional
  85. information you feel may be helpful will be appreciated.
  86. <P>
  87. <UL>
  88. <LI>Version information (output of -V)
  89. </LI>
  90. <LI>Command line used (options and arguments)
  91. </LI>
  92. <LI>Platform (Red Hat Linux 9 on Intel, Solaris 7 on SPARC, etc)
  93. </LI>
  94. <LI>Error message (if available) and/or description of problem
  95. </LI>
  96. <LI>If possible, attach the pcap file used (compressed with bzip2 or gzip
  97. preferred)
  98. </LI>
  99. <LI>The core dump or backtrace if available
  100. </LI>
  101. </UL>
  102. <P>
  103. <H2><A NAME="SECTION00033000000000000000">
  104. <SPAN CLASS="arabic">2</SPAN>.<SPAN CLASS="arabic">3</SPAN> I have a feature request, what should I do?</A>
  105. </H2>
  106. <P>
  107. Let us know! Many of the features exist today because users like you
  108. asked for them. To make a feature request, you can either email the
  109. tcpreplay-users mailing list (see above) or fill out the feature request
  110. form on the tcpreplay SourceForge website.
  111. <P>
  112. <H2><A NAME="SECTION00034000000000000000">
  113. <SPAN CLASS="arabic">2</SPAN>.<SPAN CLASS="arabic">4</SPAN> I've written a patch for tcpreplay, how can I submit it?</A>
  114. </H2>
  115. <P>
  116. I'm always willing to include new features or bug fixes submitted
  117. by users. You may email me directly or the tcpreplay-users mailing
  118. list. Please <SPAN CLASS="textit">do not</SPAN> use the Patch Tracker on the tcpreplay
  119. SourceForge web site. But before you start working on adding a feature
  120. or fixing a bug in tcpreplay, please make sure you checkout the latest
  121. source code from the Subversion repository. Patches against released
  122. versions are almost surely not going to apply cleanly if at all.
  123. <P>
  124. <H2><A NAME="SECTION00035000000000000000">
  125. <SPAN CLASS="arabic">2</SPAN>.<SPAN CLASS="arabic">5</SPAN> Patch requirements</A>
  126. </H2>
  127. <P>
  128. <UL>
  129. <LI>Be aware that submitting a patch, <SPAN CLASS="textit">you are assigning your copyright
  130. to me.</SPAN> If this is not acceptable to you, then <SPAN CLASS="textit">do not</SPAN> send
  131. me the patch! I have people assign their copyright to me to help prevent
  132. licensing issues that may crop up in the future.
  133. </LI>
  134. <LI>Please provide a description of what your patch does!
  135. </LI>
  136. <LI>Comment your code! I won't use code I can't understand.
  137. </LI>
  138. <LI>Make sure you are patching a branch that is still being maintained.
  139. Generally that means that most recent stable and development branches
  140. (2.0 and 3.0 at the time of this writing).
  141. </LI>
  142. <LI>Make sure you are patching against the most recent release for that
  143. branch.
  144. </LI>
  145. <LI>Please submit your patch in the unified diff format so I can better
  146. understand what you're changing.
  147. </LI>
  148. <LI>Please provide any relevant personal information you'd like listed
  149. in the CREDITS file.
  150. </LI>
  151. </UL>
  152. Please note that while I'm always interested in patches, I may rewrite
  153. some or all of your submission to maintain a consistent coding style.
  154. <P>
  155. <DIV CLASS="navigation"><HR>
  156. <!--Navigation Panel-->
  157. <A NAME="tex2html156"
  158. HREF="node4.html">
  159. <IMG WIDTH="37" HEIGHT="24" ALIGN="BOTTOM" BORDER="0" ALT="next" SRC="next.png"></A>
  160. <A NAME="tex2html152"
  161. HREF="FAQ.html">
  162. <IMG WIDTH="26" HEIGHT="24" ALIGN="BOTTOM" BORDER="0" ALT="up" SRC="up.png"></A>
  163. <A NAME="tex2html146"
  164. HREF="node2.html">
  165. <IMG WIDTH="63" HEIGHT="24" ALIGN="BOTTOM" BORDER="0" ALT="previous" SRC="prev.png"></A>
  166. <A NAME="tex2html154"
  167. HREF="node1.html">
  168. <IMG WIDTH="65" HEIGHT="24" ALIGN="BOTTOM" BORDER="0" ALT="contents" SRC="contents.png"></A>
  169. <BR>
  170. <B> Next:</B> <A NAME="tex2html157"
  171. HREF="node4.html">3 Understanding tcpprep</A>
  172. <B> Up:</B> <A NAME="tex2html153"
  173. HREF="FAQ.html">Tcpreplay 3.x FAQ</A>
  174. <B> Previous:</B> <A NAME="tex2html147"
  175. HREF="node2.html">1 General Info</A>
  176. &nbsp; <B> <A NAME="tex2html155"
  177. HREF="node1.html">Contents</A></B> </DIV>
  178. <!--End of Navigation Panel-->
  179. <ADDRESS>
  180. Aaron Turner
  181. 2005-08-07
  182. </ADDRESS>
  183. </BODY>
  184. </HTML>