upstream/openldap
1
0
Fork 0
mirror of https://git.openldap.org/openldap/openldap.git synced 2026-02-03 20:40:05 -05:00
Code Issues Projects Releases Packages Wiki Activity Actions

ITS#5312 - input must conform to RFC2849

Browse source
This commit is contained in:
Howard Chu 2008-01-09 15:58:34 +00:00
parent 5a143df3ce
commit adbe551561
1 changed files with 2 additions and 33 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

35
doc/man/man1/ldapmodify.1
View file

@ -243,40 +243,9 @@ Issue StartTLS (Transport Layer Security) extended operation. If you use
, the command will require the operation to be successful.
.SH INPUT FORMAT
The contents of \fIfile\fP (or standard input if no \-f flag is given on
the command line) should conform to the format defined in
.BR ldif (1)
(LDIF as defined RFC 2849), or
.BR slapd.replog (5)
(an extended form of LDIF)
with the exceptions noted below.
.LP
Lines that begin with "replica:" are matched against the LDAP server host
and port in use to decide if a particular replog record should be applied.
Any other lines that precede the "dn:" line are ignored.
The -F flag can be used to force
.I ldapmodify
to apply all of the replog changes, regardless of the presence or
absence of any "replica:" lines.
.LP
If no "changetype:" line is present, the default is "add" if the -a
flag is set (or if the program was invoked as
.I ldapadd)
and "modify" otherwise.
.LP
If changetype is "modify" and no "add:", "replace:", or "delete:" lines
appear, the default is "replace" for
.BR ldapmodify (1)
and "add" for
.BR ldapadd (1).
.LP
Note that the above exceptions to the
.BR slapd.replog (5)
format allow
the command line) must conform to the format defined in
.BR ldif (5)
entries to be used as input to
.I ldapmodify
or
.I ldapadd.
(LDIF as defined RFC 2849).
.SH EXAMPLES
Assuming that the file
.B /tmp/entrymods