个人工具
登录
查看“OpenLDAPAdminGuide/ConfiguringSlapd”的源代码 - Ubuntu中文
页面
讨论
查看源代码
历史
搜索
导航
首页
最近更改
随机页面
页面分类
帮助
编辑
编辑指南
沙盒
新闻动态
字词处理
工具
链入页面
相关更改
特殊页面
页面信息
查看“OpenLDAPAdminGuide/ConfiguringSlapd”的源代码
来自Ubuntu中文
←
OpenLDAPAdminGuide/ConfiguringSlapd
跳转至:
导航
,
搜索
因为以下原因,你没有权限编辑本页:
您所请求的操作仅限于该用户组的用户使用:
用户
您可以查看与复制此页面的源代码。
==== Configuration Layout(配置规划) ==== The slapd configuration is stored as a special LDAP directory with a predefined schema and DIT. There are specific objectClasses used to carry global configuration options, schema definitions, backend and database definitions, and assorted other items. A sample config tree is shown in Figure 5.1.<br> slapd 配置被当作一个有着预定义模式和DIT的特殊 LDAP 目录来保存。在那里特定的 objectClasses 被用来支持全局配置选项、模式定义、后台和数据库定义以及其它各项。图 5.1 显示了一个配置树示例: attechment:config_dit.gif Other objects may be part of the configuration but were omitted from the illustration for clarity.<br> 其它配置对象部分为了能说明清楚而被忽略。 The slapd.d configuration tree has a very specific structure. The root of the tree is named cn=config and contains global configuration settings. Additional settings are contained in separate child entries:<br> slapd.d 配置树有个非常特殊结构。树根被命名为 cn=config 并包含全局配置设置。附加设置被包含在特定的子条目中: * Include files (包含文件) ** Usually these are just pathnames left over from a converted slapd.conf file.<br>通常是从已被转换的 slapd.conf 文件所残留下来的路径名 ** Otherwise use of Include files is deprecated.<br>否则并不留成使用包含文件 * Dynamically loaded modules(动态引导模块) ** These may only be used if the --enable-modules option was used to configure the software.<br>这只有在编译软件时使用 --enable-modules 选项才能使用 * Schema definitions(模式定义) ** The cn=schema,cn=config entry contains the system schema (all the schema that is hard-coded in slapd).<br> cn=schema,cn=config 条目包含系统模式(在 slapd 中所有模式都是硬编码) ** Child entries of cn=schema,cn=config contain user schema as loaded from config files or added at runtime.<br>cn=schema,cn=config 的子条目包含在运行时从配置文件引导或添加的用户模式。 * Backend-specific configuration(特定后台配置) * Database-specific configuration(特定数据库配置) ** Overlays are defined in children of the Database entry.<br>覆盖定义数据库子条目 ** Databases and Overlays may also have other miscellaneous children.<br>数据库和覆盖定义也可以有其它各种子条目 The usual rules for LDIF files apply to the configuration information: Comment lines beginning with a '#' character are ignored. If a line begins with a single space, it is considered a continuation of the previous line (even if the previous line is a comment) and the single leading space is removed. Entries are separated by blank lines.<br> LDIF 文件的通用规则应用于配置信息:用 # 号开始的注释行被忽略。如果是以单个空格开始的行,那么它被认为是前一行的延续(甚至前一行是注释行也一样)同样删除该空格。条目之间用空行分隔。 The general layout of the config LDIF is as follows:<br> LDIF 配置的常见形式如下所示: * <pre><nowiki> # global configuration settings dn: cn=config objectClass: olcGlobal cn: config <global config settings> # schema definitions 模式定义 dn: cn=schema,cn=config objectClass: olcSchemaConfig cn: schema <system schema> dn: cn={X}core,cn=schema,cn=config objectClass: olcSchemaConfig cn: {X}core <core schema> # additional user-specified schema 用户指定的额外模式 ... # backend definitions 后台定义 dn: olcBackend=<typeA>,cn=config objectClass: olcBackendConfig olcBackend: <typeA> <backend-specific settings> # database definitions 数据库定义 dn: olcDatabase={X}<typeA>,cn=config objectClass: olcDatabaseConfig olcDatabase: {X}<typeA> <database-specific settings> # subsequent definitions and settings 随后的定义和设置 ... </nowiki></pre> Some of the entries listed above have a numeric index "{X}" in their names. While most configuration settings have an inherent ordering dependency (i.e., one setting must take effect before a subsequent one may be set), LDAP databases are inherently unordered. The numeric index is used to enforce a consistent ordering in the configuration database, so that all ordering dependencies are preserved. In most cases the index does not have to be provided; it will be automatically generated based on the order in which entries are created.<br> 上面所列的某些条目名称中有一个数据索引 "{X}"。因为大多数配置设定都有一个固定顺序(如一个设定必须在其后可能被设置的设定之前发生作用),而LDAP 数据库天生是没有次序的。 Configuration directives are specified as values of individual attributes. Most of the attributes and objectClasses used in the slapd configuration have a prefix of "olc" (OpenLDAP Configuration) in their names. Generally there is a one-to-one correspondence between the attributes and the old-style slapd.conf configuration keywords, using the keyword as the attribute name, with the "olc" prefix attached.<br> 配置指令作为单个属性值。大多数用在 slapd 配置的属性和 objectClass,在它们的名字中都有 “olc“ 的前缀(OpenLDAP 配置)。通常在属性和老的 slapd.conf 配置关键字之间存在着一一对应的关系,一般使用带 “olc“ 前缀的关键字做为属性名。 A configuration directive may take arguments. If so, the arguments are separated by white space. If an argument contains white space, the argument should be enclosed in double quotes "like this". In the descriptions that follow, arguments that should be replaced by actual text are shown in brackets <>.<br> 配置语句是可以有参数,如果是那样的话,参数之间用空白符分隔。如果参数中包含空白符,那么参数将被双引号引起来,"就象这样"。在接下来的说明中,显示在 <> 尖括号中的参数应该用实际文本替代。 The distribution contains an example configuration file that will be installed in the /usr/local/etc/openldap directory. A number of files containing schema definitions (attribute types and object classes) are also provided in the /usr/local/etc/openldap/schema directory.<br> 发行版中包含的配置文件样本被安装在 /usr/local/etc/openldap 目录中。而在 /usr/local/etc/openldap/schema 目录中也提供了大量包含着 schema 定义(属性类型和对象类)的文件。
返回至
OpenLDAPAdminGuide/ConfiguringSlapd
。