Commit 21d48622 authored by Ondřej Kuzník's avatar Ondřej Kuzník
Browse files

ITS#9559 mod_next is not there anymore

parent b92b0337
Pipeline #2725 passed with stage
in 47 minutes and 30 seconds
......@@ -60,7 +60,6 @@ defined below.
char **modv_strvals;
struct berval **modv_bvals;
} mod_vals;
struct ldapmod *mod_next;
} LDAPMod;
#define mod_values mod_vals.modv_strvals
#define mod_bvalues mod_vals.modv_bvals
......@@ -71,9 +70,7 @@ The \fImod_op\fP field is used to specify the type of modification to
perform and should be one of LDAP_MOD_ADD, LDAP_MOD_DELETE, or
LDAP_MOD_REPLACE. The \fImod_type\fP and \fImod_values\fP fields
specify the attribute type to modify and a null-terminated array of
values to add, delete, or replace respectively. The \fImod_next\fP
field is used only by the LDAP server and may be ignored by the
client.
values to add, delete, or replace respectively.
.LP
If you need to specify a non-string value (e.g., to add a
photo or audio attribute value), you should set \fImod_op\fP to the
......
Markdown is supported
0% or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment