From: https://me.yahoo.com/hanki_pank#f42c5 <Christof_Hanke@web>
Date: Tue, 26 Oct 2010 08:59:48 +0000 (-0700)
Subject: (no commit message)
X-Git-Url: https://git.openafs.org/?p=openafs-wiki.git;a=commitdiff_plain;h=aa30decaff1cb2941eef8ad9ae6323a6ba8075d3

---

diff --git a/AFSLore/debugging.mdwn b/AFSLore/debugging.mdwn
index 9b34287..6489be8 100644
--- a/AFSLore/debugging.mdwn
+++ b/AFSLore/debugging.mdwn
@@ -15,7 +15,7 @@ Then we need to attach the gdb and make it display the stack of all threads :
     
     gdb --batch --eval-command="thread apply all where" $SRV_PATH $PID > /tmp/threads.log
 
-After this you might use the attached script "threadLogParser.py" to display the intersting threads.
+After this you might use the attached script [[threadLogParser.py]] to display the intersting threads.
 
 e.g.
 
@@ -30,10 +30,13 @@ Low-level debugging of a client can be done using "fstrace". <br/>
 Unfortunately, this produces a lot of output, so it is not easy 
 to catch an intermittent error-condition with "fstrace".
 
-The attached script "ClientTracing.py" gives you the opportunity to continuously run a fstrace, <br/>
+The attached script [[ClientTracing.py]] gives you the opportunity to continuously run a fstrace, <br/>
 where the output is stored in rotating log-files. 
 
 In case of an external-event (the existence of a predefined file), it saves this log and does not overwrite
 it again.<br/>
 Thus, all you need to do is to write a script which creates this predefined file, when that event happens.
 
+
+
+