(no commit message)

[openafs-wiki.git] / debugging.mdwn

diff --git a/debugging.mdwn b/debugging.mdwn
index 053ad21..5301179 100644 (file)
--- a/debugging.mdwn
+++ b/debugging.mdwn
@@ -51,7 +51,7 @@ To disable the tracing when you are done:
 
 ### intermittent issues
 
-Unfortunately, "fsrace" produces a lot of output, so it is may not be easy to catch an intermittent error-condition, since fstrace uses a ring buffer.
+Unfortunately, "fstrace" produces a lot of output, so it is may not be easy to catch an intermittent error-condition.
 
 The attached script [[ClientTracing.py]] (presently for Unix only) gives you the opportunity to continuously run a fstrace, <br/>
 where the output is stored in rotating log-files. 
@@ -62,4 +62,4 @@ Thus, all you need to do is to write a script which creates this predefined file
 
 ### defined issue
 
-When you exactly know how to reproduce the issue, or you don't want to install python on your client, you can use the attached script [[ClientTracing.bat]] (for Windows only). It is setting up the client tracing, starting up a tshark (terminal-version of wireshark) and waits for you to tell it to stop tracing. In order to synchronize the timestamps of the wireshark log and the afsd-trace-log, a "dir \\AFS\openafs.org" is issued on startup. The logfiles are copied to a predefined directory. The script itself should be self-explanatory.]
+When you exactly know how to reproduce the issue, or you don't want to install python on your client, you can use the attached script [[ClientTracing.bat]] (for Windows only). It is setting up the client tracing, starting up a tshark (terminal-version of wireshark) and waits for you to tell it to stop tracing. In order to synchronize the timestamps of the wireshark log and the afsd-trace-log, a "dir \\\\AFS\grand.central.org" is issued on startup. The logfiles are copied to a predefined directory. The script itself should be self-explanatory.]