From 2bbd79d4eb6b712f80364ddd9e3549de30529674 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Petr=20P=C3=ADsa=C5=99?= Date: Wed, 12 Jan 2011 16:30:53 +0100 Subject: [PATCH] Correct --no-mixed-pathnames documentation This option controls a leading slash, not a trailing one. The quota(1) page talks about quota, not about setquota. --- edquota.8 | 2 +- quota.1 | 4 ++-- setquota.8 | 2 +- 3 files changed, 4 insertions(+), 4 deletions(-) diff --git a/edquota.8 b/edquota.8 index 9b7ffd4..4b1406b 100644 --- a/edquota.8 +++ b/edquota.8 @@ -101,7 +101,7 @@ Currently, pathnames of NFSv4 mountpoints are sent without leading slash in the uses this to recognize NFSv4 mounts and properly prepend pseudoroot of NFS filesystem to the path. If you specify this option, .BR edquota -will always send paths with a trailing slash. This can be useful for legacy reasons but +will always send paths with a leading slash. This can be useful for legacy reasons but be aware that quota over RPC will stop working if you are using new .BR rpc.rquotad . .TP diff --git a/quota.1 b/quota.1 index 11865af..7a62764 100644 --- a/quota.1 +++ b/quota.1 @@ -123,8 +123,8 @@ Currently, pathnames of NFSv4 mountpoints are sent without leading slash in the .BR rpc.rquotad uses this to recognize NFSv4 mounts and properly prepend pseudoroot of NFS filesystem to the path. If you specify this option, -.BR setquota -will always send paths with a trailing slash. This can be useful for legacy reasons but +.BR quota +will always send paths with a leading slash. This can be useful for legacy reasons but be aware that quota over RPC will stop working if you are using new .BR rpc.rquotad . .TP diff --git a/setquota.8 b/setquota.8 index c7fe408..472279d 100644 --- a/setquota.8 +++ b/setquota.8 @@ -126,7 +126,7 @@ Currently, pathnames of NFSv4 mountpoints are sent without leading slash in the uses this to recognize NFSv4 mounts and properly prepend pseudoroot of NFS filesystem to the path. If you specify this option, .BR setquota -will always send paths with a trailing slash. This can be useful for legacy reasons but +will always send paths with a leading slash. This can be useful for legacy reasons but be aware that quota over RPC will stop working if you are using new .BR rpc.rquotad . .TP -- 1.7.3.4