summaryrefslogtreecommitdiff
path: root/tools/regression/file/dup/dup.c
diff options
context:
space:
mode:
authorUlrich Spörlein <uqs@FreeBSD.org>2011-12-30 00:04:11 +0000
committerUlrich Spörlein <uqs@FreeBSD.org>2011-12-30 00:04:11 +0000
commit8ce070c1b28cd5f33c098da43378d0239091bd00 (patch)
tree10328638ca028de0f11cc798a2fd1593af0e720c /tools/regression/file/dup/dup.c
parent020d387e5b4fab13879c0b55d5739178673e5231 (diff)
Notes
Diffstat (limited to 'tools/regression/file/dup/dup.c')
-rw-r--r--tools/regression/file/dup/dup.c2
1 files changed, 1 insertions, 1 deletions
diff --git a/tools/regression/file/dup/dup.c b/tools/regression/file/dup/dup.c
index d6dd0ffd313fe..b0d9af2fa9ff5 100644
--- a/tools/regression/file/dup/dup.c
+++ b/tools/regression/file/dup/dup.c
@@ -104,7 +104,7 @@ main(int __unused argc, char __unused *argv[])
* Normally dup and dup2 will clear the close-on-exec
* flag on the new fd (which appears to be an implementation
* mistake from start and not some planned behavior).
- * In todays implementations of dup and dup2 we have to make
+ * In today's implementations of dup and dup2 we have to make
* an effort to really clear that flag. But all tested
* implementations of dup2 have another tweak. If we
* dup2(old, new) when old == new, the syscall short-circuits