summaryrefslogtreecommitdiff
path: root/docs-xml
diff options
context:
space:
mode:
authorMathieu Parent <math.parent@gmail.com>2019-08-29 22:37:10 +0200
committerAndrew Bartlett <abartlet@samba.org>2019-09-01 22:21:28 +0000
commitb688926cd9e51a27b91ad5f9efe92af837e5e65c (patch)
tree1fe219e2734d22a92030e68037cf77c7bce392d7 /docs-xml
parentd6525485df9c1e06206df2239d3069eb180c6768 (diff)
downloadsamba-b688926cd9e51a27b91ad5f9efe92af837e5e65c.tar.gz
Spelling fixes s/touble/trouble/
Signed-off-by: Mathieu Parent <math.parent@gmail.com> Reviewed-by: Andrew Bartlett <abartlet@samba.org> Reviewed-by: Gary Lockyer <gary@catalyst.net.nz>
Diffstat (limited to 'docs-xml')
-rw-r--r--docs-xml/Samba-Developers-Guide/Tracing.xml2
1 files changed, 1 insertions, 1 deletions
diff --git a/docs-xml/Samba-Developers-Guide/Tracing.xml b/docs-xml/Samba-Developers-Guide/Tracing.xml
index 96f15ccc42d..50ad2eeb37b 100644
--- a/docs-xml/Samba-Developers-Guide/Tracing.xml
+++ b/docs-xml/Samba-Developers-Guide/Tracing.xml
@@ -104,7 +104,7 @@ that smbd makes.
<para>
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
+happens. For example, if I am having trouble with permissions on a file
I would search for that files name in the strace output and look at
the surrounding lines. Another trick is to match up file descriptor
numbers and "follow" what happens to an open file until it is closed.