summaryrefslogtreecommitdiff
path: root/doc/s6-sudoc.html
diff options
context:
space:
mode:
authorLaurent Bercot <ska-skaware@skarnet.org>2014-12-20 02:52:53 +0000
committerLaurent Bercot <ska-skaware@skarnet.org>2014-12-20 02:52:53 +0000
commit9059c09ef1e5e71d3b63754bbe1277338070955b (patch)
tree0a3366fb574146f9dcddc0393ca625f1b4d4a3bb /doc/s6-sudoc.html
parent28ffb0356f13499927bad7bbcf66f63f7208828f (diff)
downloads6-networking-9059c09ef1e5e71d3b63754bbe1277338070955b.tar.xz
Doc fixes
Diffstat (limited to 'doc/s6-sudoc.html')
-rw-r--r--doc/s6-sudoc.html2
1 files changed, 1 insertions, 1 deletions
diff --git a/doc/s6-sudoc.html b/doc/s6-sudoc.html
index 0ca9918..def09a9 100644
--- a/doc/s6-sudoc.html
+++ b/doc/s6-sudoc.html
@@ -65,7 +65,7 @@ default, <em>timeoutrun</em> is 0, meaning infinite. </li>
while the server program is still running, s6-sudod will send a SIGTERM and a
SIGCONT to the server program - but this does not guarantee that it will die.
If the server program keeps running, it might still read from the file that
-was s6-sudoc's stdin, or write to the files that were s6-sudod's stdout or
+was s6-sudoc's stdin, or write to the files that were s6-sudoc's stdout or
stderr. <strong>This is a potential security risk</strong>.
Administrators should audit their server programs to make sure this does not
happen. </li>