summaryrefslogtreecommitdiffstats
path: root/sys/kern/kern_exec.c
diff options
context:
space:
mode:
authorbdrewery <bdrewery@FreeBSD.org>2016-03-01 23:58:53 +0000
committerbdrewery <bdrewery@FreeBSD.org>2016-03-01 23:58:53 +0000
commit199dda9a012b64a9c3ab64f9ad7a09f4503c9bdc (patch)
tree4c85b02d42e6572b24640364806ec3cceb711238 /sys/kern/kern_exec.c
parentbfbda68e27410570c7574288c2a1ed27d795a743 (diff)
downloadFreeBSD-src-199dda9a012b64a9c3ab64f9ad7a09f4503c9bdc.zip
FreeBSD-src-199dda9a012b64a9c3ab64f9ad7a09f4503c9bdc.tar.gz
Correct a comment.
Diffstat (limited to 'sys/kern/kern_exec.c')
-rw-r--r--sys/kern/kern_exec.c2
1 files changed, 1 insertions, 1 deletions
diff --git a/sys/kern/kern_exec.c b/sys/kern/kern_exec.c
index 741bc3e..69f0774 100644
--- a/sys/kern/kern_exec.c
+++ b/sys/kern/kern_exec.c
@@ -676,7 +676,7 @@ interpret:
* Don't honor setuid/setgid if the filesystem prohibits it or if
* the process is being traced.
*
- * We disable setuid/setgid/etc in compatibility mode on the basis
+ * We disable setuid/setgid/etc in capability mode on the basis
* that most setugid applications are not written with that
* environment in mind, and will therefore almost certainly operate
* incorrectly. In principle there's no reason that setugid
OpenPOWER on IntegriCloud