summaryrefslogtreecommitdiff
path: root/docs/textdocs/Tracing.txt
diff options
context:
space:
mode:
authorAndrew Tridgell <tridge@samba.org>2002-07-15 10:35:28 +0000
committerAndrew Tridgell <tridge@samba.org>2002-07-15 10:35:28 +0000
commite90b65284812aaa5ff9e9935ce9bbad7791cbbcd (patch)
tree9e744d1dc2f93934a4b49166a37383d3cb2b2139 /docs/textdocs/Tracing.txt
parentec167dc9cc0ec2ee461837c25a371d2981744208 (diff)
downloadsamba-e90b65284812aaa5ff9e9935ce9bbad7791cbbcd.tar.gz
samba-e90b65284812aaa5ff9e9935ce9bbad7791cbbcd.tar.bz2
samba-e90b65284812aaa5ff9e9935ce9bbad7791cbbcd.zip
updated the 3.0 branch from the head branch - ready for alpha18
(This used to be commit 03ac082dcb375b6f3ca3d810a6a6367542bc23ce)
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