upstream/openldap
1
0
Fork 0
mirror of https://git.openldap.org/openldap/openldap.git synced 2025-12-30 19:49:35 -05:00
Code Issues Projects Releases Packages Wiki Activity Actions

Update references to RFCs

Browse source
This commit is contained in:
Kurt Zeilenga 2000-09-01 22:10:19 +00:00
parent 84d0e26234
commit 5ed98aed27
4 changed files with 10 additions and 10 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

6
doc/man/man3/ldap_get_dn.3
View file

@ -34,9 +34,9 @@ char *dn;
.SH DESCRIPTION
These routines allow LDAP entry names (Distinguished Names, or DNs)
to be obtained, parsed, converted to a user-friendly form, and tested.
A DN has the form described in RFC 1779 "A String Representation of
Distinguished Names", unless it is an experimental DNS-style DN
which takes the form of an RFC 822 mail address.
A DN has the form described in
RFC 2253 "Lightweight Directory Access Protocol (v3):
UTF-8 String Representation of Distinguished Names".
.LP
The
.B ldap_get_dn()

8
doc/man/man3/ldap_schema.3
View file

@ -114,13 +114,13 @@ char * ldap_scherr2str(code)
int code;
.SH DESCRIPTION
These routines are used to parse schema definitions in the syntax
defined in RFC2252 into structs and handle these structs. These
defined in RFC 2252 into structs and handle these structs. These
routines handle four kinds of definitions: syntaxes, matching rules,
attribute types and objectclasses. For each definition kind, four
routines are provided.
.LP
.B ldap_str2xxx()
takes a definition in RFC2252 format in argument
takes a definition in RFC 2252 format in argument
.IR s
as a NUL-terminated string and returns, if possible, a pointer to a
newly allocated struct of the appropriate kind. The caller is
@ -142,7 +142,7 @@ is a bit mask of parsing options controlling the relaxation of the
syntax recognized. The following values are defined:
.TP
.B LDAP_SCHEMA_ALLOW_NONE
strict parsing according to RFC2252.
strict parsing according to RFC 2252.
.TP
.B LDAP_SCHEMA_ALLOW_NO_OID
permit definitions that do not contain an initial OID.
@ -275,7 +275,7 @@ return a canonical name for the definition.
.LP
Routines
.B ldap_xxx2str()
return a string representation in the format described by RFC2252 of
return a string representation in the format described by RFC 2252 of
the struct passed in the argument. The string is a newly allocated
string that must be freed by the caller. These routines may return
NULL if no memory can be allocated for the string.

4
doc/man/man3/ldap_search.3
View file

@ -75,7 +75,7 @@ BNF:
.LP
The '~=' construct is used to specify approximate matching. The
representation for <attributetype> and <attributevalue> are as
described in RFC 1778. In addition, <attributevalue> can be a single *
described in RFC 2254. In addition, <attributevalue> can be a single *
to achieve an attribute existence test, or can contain text and *'s
interspersed to achieve substring matching.
.LP
@ -83,7 +83,7 @@ For example, the filter "mail=*" will find any entries that have a mail
attribute. The filter "mail=*@terminator.rs.itd.umich.edu" will find
any entries that have a mail attribute ending in the specified string.
To put parentheses in a filter, escape them with a backslash '\\'
character. See RFC 1588 for a more complete description of allowable
character. See RFC 2254 for a more complete description of allowable
filters. See
.BR ldap_getfilter (3)
for routines to help in constructing search filters automatically.

2
doc/man/man8/go500gw.8
View file

@ -91,7 +91,7 @@ file is given below, with the things you should change given in <>'s:
Name=<Label of your choice>
Type=1
Port=7777
Path=1<optional RFC 1779-format DN at which to start browsing>
Path=1<optional RFC 2253-format DN at which to start browsing>
Host=<host.running.go500gw.here>
.ft
.fi