summaryrefslogtreecommitdiffstats
path: root/share/man/man9/namei.9
diff options
context:
space:
mode:
authorhoek <hoek@FreeBSD.org>2000-05-21 03:23:10 +0000
committerhoek <hoek@FreeBSD.org>2000-05-21 03:23:10 +0000
commite6e653134b60dfde02617f37dcd4343b8efabc6c (patch)
tree15df009891ff1c1a0cb2bcc015e6aeb755129e03 /share/man/man9/namei.9
parentd5d9f7eb9e8ae206cee16bb6de80f20e1d439903 (diff)
downloadFreeBSD-src-e6e653134b60dfde02617f37dcd4343b8efabc6c.zip
FreeBSD-src-e6e653134b60dfde02617f37dcd4343b8efabc6c.tar.gz
The LOCKPARENT flag is singular. It doesn't work causing complications
is also a singular fact.
Diffstat (limited to 'share/man/man9/namei.9')
-rw-r--r--share/man/man9/namei.94
1 files changed, 2 insertions, 2 deletions
diff --git a/share/man/man9/namei.9 b/share/man/man9/namei.9
index 5f40c2b..1eb8ad2 100644
--- a/share/man/man9/namei.9
+++ b/share/man/man9/namei.9
@@ -194,9 +194,9 @@ if SAVESTART or SAVENAME is set.
To free only the ni_cnd.cn_pnbuf, there is a special flags NDF_ONLY_PNBUF.
To not free the cnd, use the flag ND_NO_FREE_PNBUF.
.Sh BUGS
-LOCKPARENT do not always result in parent vp being locked (see details in
+LOCKPARENT does not always result in parent vp being locked (see details in
description).
-This result in complications everywhere LOCKPARENT is used.
+This results in complications everywhere LOCKPARENT is used.
In order to solve this for the cases that include both LOCKPARENT and LOCKLEAF,
it will be necessary to go to recursive locking.
.Sh SEE ALSO
OpenPOWER on IntegriCloud