
28 Novell eDirectory 8.8 SP7 Troubleshooting Guide
5.1.2 LDIF Content Records
An LDIF content record represents the contents of an entire entry. The following is an example of an
LDIF file with four content records:
1 version: 1
2 dn: c=US
3 objectClass: top
4 objectClass: country
5
6 dn: l=San Francisco, c=US
7 objectClass: top
8 objectClass: locality
9 st: San Francisco
10
11 dn: ou=Artists, l=San Francisco, c=US
12 objectClass: top
13 objectClass: organizationalUnit
14 telephoneNumber: +1 415 555 0000
15
16 dn: cn=Peter Michaels, ou=Artists, l=San Francisco, c=US
17 sn: Michaels
18 givenname: Peter
19 objectClass: top
20 objectClass: person
21 objectClass: organizationalPerson
22 objectClass: iNetOrgPerson
23 telephonenumber: +1 415 555 0001
25 userpassword: Peter123
26
This LDIF file is composed of the following parts:
Component Description
Version Specifier The first line of an LDIF file contains the version. Zero or more
spaces are allowed between the colon and the version number,
which is currently defined to be 1.
If the version line is missing, any application processing the LDIF
file is allowed to assume that the file is version 0. It’s also possible
that the LDIF file could be rejected as syntactically incorrect. Novell
utilities that process LDIF assume a file version of 0 when the
version line is missing.
Distinguished Name Specifier The first line of every content record (lines 2, 6, 11, and 16 in the
example above) specifies the DN of the entry that it represents.
The DN specifier must take one of the following two forms:
dn: safe_UTF-8_distinguished_name
dn:: Base64_encoded_distinguished_name
Line Delimiters The line separator can be either a line feed or a carriage return/line
feed pair. This resolves a common incompatibility between Linux
and Solaris text files, which use a line feed as the line separator,
and MS-DOS* and Windows text files, which use a carriage return/
line feed pair as the line separator.
Comentarios a estos manuales