simon at arlott
Aug 28, 2011, 11:38 AM
Post #1 of 2
(190 views)
Permalink
|
|
Syntax errors in spec.xfpt
|
|
Tried to build the latest git code and failed on the documentation:
xfpt spec.xfpt
** Error: missing closing flag %&
Detected near line 27349 of spec.xfpt
** Error: missing closing flag %&
Detected near line 27349 of spec.xfpt
** Error: missing semicolon after "&unique"
Detected near line 27402 of spec.xfpt
** Error: unknown flag "& "
Detected near line 27402 of spec.xfpt
The following changes since commit 52ba4661114d0a96c15f5f43bcb97ce89061f1b6:
Pull strict-aliasing fix for sockaddr_46. (2011-07-06 11:19:17 -0400)
are available in the git repository at:
git://github.com/lp0/exim.git for-upstream
Simon Arlott (1):
fix xfpt syntax errors
doc/doc-docbook/spec.xfpt | 4 ++--
1 files changed, 2 insertions(+), 2 deletions(-)
diff --git a/doc/doc-docbook/spec.xfpt b/doc/doc-docbook/spec.xfpt
index e920135..71d931a 100644
--- a/doc/doc-docbook/spec.xfpt
+++ b/doc/doc-docbook/spec.xfpt
@@ -27323,7 +27323,7 @@ checks.
The &%per_*%& options described above do not make sense in some ACLs. If you
use a &%per_*%& option in an ACL where it is not normally permitted then the
-update mode defaults to &%readonly%& and you cannot specify the &%strict&% or
+update mode defaults to &%readonly%& and you cannot specify the &%strict%& or
&%leaky%& modes. In other ACLs the default update mode is &%leaky%& (see the
next section) so you must specify the &%readonly%& option explicitly.
@@ -27377,7 +27377,7 @@ go over the limit is not added to the set, in the same way that the client's
recorded rate is not updated in the same situation.
When you combine the &%unique=%& and &%readonly%& options, the specific
-%&unique=%& value is ignored, and Exim just retrieves the client's stored
+&%unique=%& value is ignored, and Exim just retrieves the client's stored
rate.
The &%unique=%& mechanism needs more space in the ratelimit database than the
--
Simon Arlott
|
smime.p7s
