doc: include debug log submission instructions in troubleshooting doc

1 files changed, 14 insertions, 10 deletions

diff --git a/doc/troubleshoot.html b/doc/troubleshoot.html
index 0f0c7fca..a0303a24 100644
--- a/doc/troubleshoot.html
+++ b/doc/troubleshoot.html
@@ -88,15 +88,19 @@ passwords or other sensitive data. If it does, you can change it to some <b>cons
 meaningless value. <b>Do not delete the lines</b>, as this renders the debug log
 unusable (and makes Rainer quite angry for wasted time, aka significantly reduces the chance
 he will remain motivated to look at your problem ;)). For the same reason, make sure
-whatever you change is change consistently. Really!
-<p>Debug log file can get quite large. Before submitting them, it is a good idea to zip them.
-Rainer has handled files of around 1 to 2 GB. If your's is larger ask before submitting. Often, 
-it is sufficient to submit the first 2,000 lines of the log file and around another 1,000 around
-the area where you see a problem. Also,
-ask you can submit a file via private mail. Private mail is usually a good way to go for large files
-or files with sensitive content. However, do NOT send anything sensitive that you do not want
-the outside to be known. While Rainer so far made effort no to leak any sensitive information,
-there is no guarantee that doesn't happen. If you need a guarantee, you are probably a
+whatever you change is changed consistently. Really!
+<p>While most debug log files are moderately large, some can get quite to extremly large.
+For those on the larger side, it is a good idea to zip them. If the file is less than
+around 100KiB, it's probably not necessary.
+<p>A good place to post your debug log is at the
+<a href="http://kb.monitorware.com/rsyslog-f40.html">rsyslog support forums</a>, together with
+your question. This also enables us to keep track of the case. The forums accept attachments in
+various common formats, but rejects others for security reasons. The zip, txt, and log extensions
+are definitely permitted, so it probably is a good idea to use one of them. For others, please
+simply try and revert to another format if the forum doesn't like what you used.
+<p>
+Please note that all information in your debug file is publically visiable.
+If this is not acceptable for you, you are probably a
 candidate for a <a href="professional_support.html">commercial support contract</a>. Free support
 comes without any guarantees, include no guarantee on confidentiality
 [aka "we don't want to be sued for work were are not even paid for ;)].
@@ -156,7 +160,7 @@ need to program or do anything else except get a problem solved ;)
 [<a href="http://www.rsyslog.com/">rsyslog site</a>]</p>
 <p><font size="2">This documentation is part of the
 <a href="http://www.rsyslog.com/">rsyslog</a> project.<br>
-Copyright &copy; 2008-2010 by <a href="http://www.gerhards.net/rainer">Rainer Gerhards</a> and
+Copyright &copy; 2008-2013 by <a href="http://www.gerhards.net/rainer">Rainer Gerhards</a> and
 <a href="http://www.adiscon.com/">Adiscon</a>. Released under the GNU GPL 
 version 3 or higher.</font></p>
 </body>