summaryrefslogtreecommitdiff
path: root/docs/textdocs/Tracing.txt
diff options
context:
space:
mode:
authorAndrew Bartlett <abartlet@samba.org>2002-06-27 14:23:48 +0000
committerAndrew Bartlett <abartlet@samba.org>2002-06-27 14:23:48 +0000
commit675a108c65834f9402d967926b30e50e811843c1 (patch)
tree1a27d670860e69981732be47f90f8db8ddf3d871 /docs/textdocs/Tracing.txt
parentb1fd1177aef97e867f7da9fe66093404baa6992c (diff)
downloadsamba-675a108c65834f9402d967926b30e50e811843c1.tar.gz
samba-675a108c65834f9402d967926b30e50e811843c1.tar.bz2
samba-675a108c65834f9402d967926b30e50e811843c1.zip
Jelmer has been keeping on top of the typos.
(This used to be commit 1e36b7e9620f616590dd9f4f44384272b62605ff)
Diffstat (limited to 'docs/textdocs/Tracing.txt')
-rw-r--r--docs/textdocs/Tracing.txt2
1 files changed, 1 insertions, 1 deletions
diff --git a/docs/textdocs/Tracing.txt b/docs/textdocs/Tracing.txt
index fd65045abd..6cc1d69258 100644
--- a/docs/textdocs/Tracing.txt
+++ b/docs/textdocs/Tracing.txt
@@ -70,7 +70,7 @@ Once you are attached you then can do whatever it is on the client
that is causing problems and you will capture all the system calls
that smbd makes.
-So how do you interpret the results? Generally I search thorugh the
+So how do you interpret the results? Generally I search through the
output for strings that I know will appear when the problem
happens. For example, if I am having touble with permissions on a file
I would search for that files name in the strace output and look at