The HP-UX Directory Server is based on an open-systems server protocol called the Lightweight
Directory Access Protocol (LDAP). The Directory Server is a robust, scalable server designed to
manage large scale directories to support an enterprise-wide directory of users and resources,
extranets, and e-commerce applications over the Internet. The Directory Server runs as the
ns-slapd process or service on the machine. The server manages the directory databases and
responds to client requests.
This reference covers the server configuration and the command-line utilities. It is designed
primarily for directory administrators and experienced directory users who want to use the
command-line to access the directory. After configuring the server, use this reference to help
maintain it.
The Directory Server can also be managed through the Directory Server Console, a graphical
user interface. The HP-UX Directory Server administrator guide describes how to do this and
explains individual administration tasks more fully.
The major components of Directory Server include:
•An LDAP server
The LDAP v3-compliant network daemon.
•Directory Server Console
A graphical management console that dramatically reduces the effort of setting up and
maintaining your directory service.
•SNMP agent
Can monitor theDirectory Server using the Simple Network Management Protocol (SNMP).
•Administration Server
Required for managing the Directory Server using the Directory Server Console.
1.1 Directory Server configuration
The format and method for storing configuration information for Directory Server and a listing
for all server attributes are found in two chapters, Chapter 2 “Core server configuration reference”
and Chapter 3 “Plug-in implemented server functionality reference”.
1.2 Directory Server instance file reference
Chapter 4 “Server instance file reference” has an overview of the files and configuration
information stored in each instance of Directory Server. This reference helps administrators
understand the changes or absence of changes in the course of directory activity. From a security
standpoint, this also helps users detect errors and intrusion by highlighting normal changes and
abnormal behavior.
1.3 Using Directory Server command-line utilities
Directory Server comes with a set of configurable command-line utilities that can search and
modify entries in the directory and administer the server. Chapter 6 “Command-line utilities”
describes these command-line utilities and contains information on where the utilities are stored
and how to access them. In addition to thesecommand-line utilities, Directory Server also provides
ns-slapd command-line utilities for performing directory operations, as described in
Appendix A “Using the ns-slapd command-line utilities”.
1.1 Directory Server configuration15
1.4 Using Directory Server command-line scripts
In addition to command-line utilities, several non-configurable scripts are provided with the
Directory Server that make it quick and easy to perform routine server administration tasks from
the command-line. Chapter 7 “Command-line scripts” lists the most frequently used scripts and
contains information on where the scripts are stored and how to access them.
16Introduction
2 Core server configuration reference
The configuration information for the HP-UX Directory Server is stored as LDAP entries within
the directory itself. Therefore, changes to the server configuration must be implemented through
the use of the server itself rather than by simply editing configuration files. The principal
advantage of this method of configuration storage is that it allows a directory administrator to
reconfigure the server using LDAP while it is still running, thus avoiding the need to shut the
server down for most configuration changes.
This chapter gives details on how the configuration is organized and how to alter it. The chapter
also provides an alphabetical reference for all attributes.
2.1 Overview of the Directory Server configuration
When the Directory Server is set up, its default configuration is stored as a series of LDAP entries
within the directory, under the subtree cn=config. When the server is started, the contents of
the cn=config subtree are read from a file (dse.ldif) in LDIF format. This dse.ldif file
contains all the server configuration information. The latest version of this file is called dse.ldif,
the version prior to the last modification is called dse.ldif.bak, and the latest file with which
the server successfully started is called dse.ldif.startOK.
Many of the features of the Directory Server are designed as discrete modules that plug into the
core server. The details of the internal configuration for each plug-in are contained in separate
entries undercn=plugins,cn=config. For example, the configuration of the Telephone Syntax
Plug-in is contained in this entry:
cn=Telephone Syntax,cn=plugins,cn=config
Similarly, database-specific configuration is stored under cn=ldbm
database,cn=plugins,cn=config for local databases and cn=chaining
database,cn=plugins,cn=config for database links.
The following diagram illustrates how the configuration data fits within the cn=config directory
information tree.
Figure 2-1 Directory information tree showing configuration data
2.1.1 LDIF and schema configuration files
The Directory Server configuration data is automatically output to files in LDIF format that are
located in the /etc/opt/dirsrv/slapd-instance_name directory. Thus, if a server identifier
is phonebook, then for a Directory Server, the configuration LDIF files are all stored under
/etc/opt/dirsrv/slapd-phonebook.
2.1 Overview of the Directory Server configuration17
This directory also contains other server instance-specific configuration files.
Schema configuration is also stored in LDIF format. The master schema directory is /etc/opt/
dirsrv/schema, and the instance-specific schema directory is
/etc/opt/dirsrv/slapd-instance_name/schema.
The following table lists all the configuration files that are supplied with the Directory Server,
including those for the schema of other compatible servers. Each file is preceded by a number
which indicates the order in which they should be loaded (in ascending numerical, then
alphabetical order).
Table 2-1 Directory Server LDIF configuration files
PurposeConfiguration file name
dse.ldif
00core.ldif
01common.ldif
05rfc2247.ldif
05rfc2927.ldif
10presence.ldif
10rfc2307.ldif
Contains front-end Directory Specific Entries created by the directory at server
startup. These include the Root DSE ("") and the contents of cn=config and
cn=monitor (acis only).
Contains only those schema definitions necessary for starting the server with the
bare minimum feature set (no user schema, no schema for any non-core features).
The rest of the schema used by users, features, and applications is found in
01common.ldif and the other schema files. Do not modify this file.
Contains LDAPv3 standard operational schema, such as subschemaSubentry,
LDAPv3 standard user and organization schema defined in RFC 2256 (based on
X.520/X.521), inetOrgPersonand other widely-used attributes, and the operational
attributes used by Directory Server configuration. Modifying this file causes
interoperability problems. User-defined attributes should be added through the
Directory Server Console.
Schema from RFC 2247 and related pilot schema, from "Using Domains in
LDAP/X500 Distinguished Names."
Schema from RFC 2927, "MIME Directory Profile for LDAP Schema." Contains the
ldapSchemas operational attribute required for the attribute to show up in the
subschema subentry.
Legacy. Schema for instant messaging presence (online) information; the file lists
the default object classes with the allowed attributes that must be added to a user's
entry in order for instant-messaging presence information to be available for that
user.
Schema from RFC 2307, "An Approach for Using LDAP as a Network Information
Service." Thismay be superseded by 10rfc2307bis, the new version of rfc2307,
when that schema becomes available.
20subscriber.ldif
25java-object.ldif
28pilot.ldif
30ns-common.ldif
50ns-admin.ldif
50ns-certificate.ldif
50ns-directory.ldif
18Core server configuration reference
Contains new schema elements and the Nortel subscriber interoperability
specification. Also contains the adminRole and memberOfattributes and
inetAdmin object class, previously stored in the 50ns-delegated-admin.ldif
file.
Schema from RFC 2713, "Schema for Representing Java®Objects in an LDAP
Directory."
Contains pilot directory schema from RFC 1274, which is no longer recommended
for new deployments. Future RFCs which succeed RFC 1274 may deprecate some
of or all 28pilot.ldif attribute types and classes.
Schema that contains objects classes and attributes common to the Directory Server
Console framework.
Schema used by the Administration Server.
Schema for Dogtag Certificate System.
Contains additional configuration schema used by DirectoryServer 4.16 and earlier
versions of the directory, which is no longer applicable to current releases of
Directory Server. This schema is required for replicating between Directory Server
4.16 and current releases.
Table 2-1 Directory Server LDIF configuration files (continued)
PurposeConfiguration file name
50ns-mail.ldif
50ns-value.ldif
50ns-web.ldif
60pam-plugin.ldif
99user.ldif
Schema used by Netscape Messaging Server to define mail users and mail groups.
Schema for servers' value item attributes.
Schema for Netscape Web Server.
Reserved for future use.
User-defined schema maintained by Directory Server replication consumers which
contains the attributes and object classes from the suppliers.
2.1.2 How the server configuration is organized
The dse.ldif file contains all configuration information including directory-specific entries
created by the directory at server startup, such as entries related tothe database. The file includes
the root Directory Server entry (or DSE, named by "") and the contents of cn=config and
cn=monitor.
When the server generates the dse.ldif file, it lists the entries in hierarchical order in the order
that the entries appear in the directory under cn=config, which is usually the same order in
which an LDAP search of subtree scope for base cn=config returns the entries.
dse.ldif also contains the cn=monitor entry, which is mostly read-only, but can have ACIs
set on it.
NOTE:
The dse.ldif file does not contain every attribute in cn=config. If the attribute has not been
set by the administrator and has a default value, the server will not write it to dse.ldif. To see
every attribute in cn=config, use the ldapsearch command.
2.1.2.1 Configuration attributes
Within a configuration entry, each attribute is represented as an attribute name. The value of the
attribute corresponds to the attribute's configuration.
The following code sample is an example of part of the dse.ldif file for a Directory Server.
The example shows, among other things, that schema checking has been enabled; this is
represented by the attribute nsslapd-schemacheck, which takes the value on.
dn: cn=config
objectclass: top
objectclass: extensibleObject
objectclass: nsslapdConfig
nsslapd-accesslog-logging-enabled: on
nsslapd-enquote-sup-oc: off
nsslapd-localhost: phonebook.example.com
nsslapd-schemacheck: on
nsslapd-port: 389
nsslapd-localuser: www
...
2.1.2.2 Configuration of plug-in functionality
The configuration for each part of Directory Server plug-in functionality has its own separate
entry and set of attributes under the subtree cn=plugins,cn=config. The following code
sample is an example of the configuration entry for an example plug-in, the Telephone Syntax
plug-in.
dn: cn=Telephone Syntax,cn=plugins,cn=config
objectclass: top
2.1 Overview of the Directory Server configuration19
Some of these attributes are common to all plug-ins, and some may be particular to a specific
plug-in. Check which attributes are currently being used by a given plug-in by performing a
search with the ldapsearch utility on the cn=config subtree.
For a list of plug-ins supported by Directory Server, general plug-in configuration information,
the plug-in configuration attribute reference, and a list of plug-ins requiring restart for
configuration changes, see Chapter 3 “Plug-in implemented server functionality reference”.
2.1.2.3 Configuration of databases
The cn=NetscapeRoot and cn=UserRoot subtrees under the database plug-in entry contain
configuration data for the databases containing the o=NetscapeRoot suffix and the default
suffix created during setup, such as dc=example,dc=com.
These entries and their children have many attributes used to configure different database settings,
like the cache sizes, the paths to the index files and transaction logs, entries and attributes for
monitoring and statistics; and database indexes.
2.1.2.4 Configuration of indexes
Configuration information for indexing is stored as entries in the Directory Server under the
following information-tree nodes:
For more information about indexes in general, see the HP-UX Directory Server administratorguide. For information about the index configuration attributes, see “Database attributes under
This section discusses access control for configuration entries and describes the various ways in
which the server configuration can be viewed and modified. It also covers restrictions to the
kinds of modification that can be made and discusses attributes that require the server to be
restarted for changes to take effect.
2.2.1 Access control for configuration entries
When the Directory Server is installed, a default set of access control instructions (ACIs) is
implemented for all entries under cn=config. The following code sample is an example of these
default ACIs.
These default ACIs allow all LDAP operations to be carried out on all configuration attributes
by the following users:
•Members of the Configuration Administrators group.
•The user acting as the administrator, the admin account that was configured at setup. By
default, this is the same user account which is logged into the Console.
20Core server configuration reference
•Members of local Directory Administrators group.
•The SIE (Server Instance Entry) group, usually assigned using the Set Access Permissions
process the main console.
For more information on access control, see the HP-UX Directory Server administrator guide.
2.2.2 Changing configuration attributes
Server attributes can be viewed and changed in one of three ways: through the Directory Server
Console, by performing ldapsearch and ldapmodify commands, or by manually editing the
dse.ldif file.
NOTE:
You must stop the server before editing the dse.ldif file; otherwise, the changes are lost.
Editing the dse.ldif file is recommended only for changes to attributes which cannot be altered
dynamically. See “Configuration changes requiring server restart” for further information.
The following sections describe how to modify entries using LDAP (both by using Directory
Server Console and by using the command line), the restrictions that apply to modifying entries,
the restrictions that apply to modifying attributes, and the configuration changes requiring
restart.
2.2.2.1 Modifying configuration entries using LDAP
The configuration entries in the directory can be searched and modified using LDAP either
through the Directory Server Console or by performing the ldapsearch and ldapmodify
operations in the same way as other directory entries. The advantage of using LDAP to modify
entries is changes can be made while the server is running.
For further information, see the chapter titled “Creating Directory Entries” in the HP-UX DirectoryServer administrator guide. However, certain changes do require the server to be restarted before
they are taken into account. See “Configuration changes requiring server restart” for further
information.
NOTE:
As with any set of configuration files, care should be taken when changing or deleting nodes in
the cn=config subtree as this risks affecting Directory Server functionality.
The entire configuration, including attributes that are set to default values, can be viewed by
performing an ldapsearch operation on the cn=config subtree:
# ldapsearch -b cn=config -D bindDN -w password
Where:
bindDN
is the DN chosen for the Directory Manager when the server was installed
(cn=Directory Manager by default).
password
is the password chosen for the Directory Manager.
For more information on using the ldapsearch command, see “ldapsearch”.
To disable a plug-in, use the ldapmodify command to edit the nsslapd-pluginEnabled
attribute:
2.2 Accessing and modifying server configuration21
2.2.2.2 Restrictions to modifying configuration entries and attributes
Certain restrictions apply when modifying server entries and attributes:
•The cn=monitor entry and its child entries are read-only and cannot be modified, except
to manage ACIs.
•If an attribute is added to cn=config, the server ignores it.
•If an invalid value is entered for an attribute, the server ignores it.
•Because the ldapdelete command is used for deleting an entire entry, use the ldapmodify
command to remove an attribute from an entry.
2.2.2.3 Configuration changes requiring server restart
Some configuration attributes cannot be altered while the server is running. In these cases, for
the changes to take effect, the server needs to be shut down and restarted. The modifications
should bemade either through the Directory Server Console or by manually editing the dse.ldif
file. Some of the attributes that require a server restart for any changes to take effect are listed
below.
2.3 Core server configuration attributes reference
This section contains reference information on the configuration attributes that are relevant to
the core server functionality. For information on changing server configuration, see “Accessing
and modifying server configuration”. For a list of server features that are implemented as plug-ins,
see “Server plug-in functionality reference”. For help with implementing custom server
functionality, contact HP support.
The configuration information stored in the dse.ldif file is organized as an information tree
under the general configuration entry cn=config, as shown in . Figure 2-1
22Core server configuration reference
Figure 2-2 Directory information tree showing configuration data
Most of these configuration tree nodes are covered in the following sections.
The cn=plugins node is covered in Chapter 3 “Plug-in implemented server functionality
reference”. The description of each attribute contains details such as the DN of its directory entry,
its default value, the valid range of values, and an example of its use.
NOTE:
Some of the entries and attributes described in this chapter may change in future releases of the
product.
2.3.1 cn=config
General configuration entries are stored in the cn=config entry. The cn=config entry is an
instance of the nsslapdConfig object class, which in turn inherits from extensibleObject
object class.
2.3.1.1 nsslapd-accesslog (Access log)
This attribute specifies the path and file name of the log used to record each LDAP access. The
following information is recorded by default in the log file:
•IP address of the client machine that accessed the database.
•Operations performed (for example, search, add, and modify).
•Result of the access (for example, the number of entries returned or an error code).
The following table describes the attribute parameters:
For more information on turning access logging off, see the "Monitoring Server and Database
Activity" chapter in the HP-UX Directory Server administrator guide.
2.3 Core server configuration attributes reference23
For access logging to be enabled, the nsslapd-accesslog attribute must contain a valid path,
and the nsslapd-accesslog-logging-enabled configuration attribute must be switched
to on. Table 2-2 lists the four possible combinations of values for these two configuration attributes
and their outcome in terms of disabling or enabling of access logging.
Table 2-2 Attribute values for enabling or disabling access logging
Value of the
Value of the nsslapd-accesslog
attribute
This attribute controls what is logged to the access log.
DescriptionParameter
Entry DN
Valid Values
cn=config
0No access logging
4Logging for internal access operations
256Logging for connections, operations, and results
512Logging for access to an entry and referrals
131072Provides microsecond operation timing
These values can be added together to provide the exact type of logging required; for
example, 516 (4 + 512) to obtain internal access operation, entry access, and referral logging.
256Default Value
on
onfilename
off
offfilename
Disabled
Enabled
Disabled
Disabled
IntegerSyntax
nsslapd-accesslog-level: 256Example
2.3.1.3 nsslapd-accesslog-list (List of access log files)
This read-only attribute, which cannot be set, provides a list of access log files used in access log
rotation.
When set to off, the server writes all access log entries directly to disk. Buffering allows the
server to use access logging even when under a heavy load without significantly impacting
performance. However, when debugging, it is sometimes useful to disable buffering in order to
see the operations and their results right away instead of having to wait for the log entries to be
24Core server configuration reference
flushed to the file. Disabling log buffering can severely impact performance in heavily loaded
servers.
This attribute specifies the maximum age that a log file is allowed to reach before it is deleted.
This attribute supplies only the number of units. The units are provided by the
nsslapd-accesslog-logexpirationtimeunit attribute.
DescriptionParameter
Entry DN
Valid Range
cn=config
–1 to the maximum 32-bit integer value (2147483647)
A value of -1 or 0 means that the log never expires.
–1Default Value
IntegerSyntax
nsslapd-accesslog-logexpirationtime: 2Example
2.3.1.6 nsslapd-accesslog-logexpirationtimeunit (Access log expiration time unit)
This attribute specifies the units for nsslapd-accesslog-logexpirationtime attribute. If
the unit is unknown by the server, then the log never expires.
Disables and enables accesslog logging but only in conjunction with the nsslapd-accesslog
attribute that specifies the path and parameter of the log used to record each database access.
The following table describes the attribute parameters.
DescriptionParameter
Entry DN
cn=config
Valid Values
on or off
onDefault Value
2.3 Core server configuration attributes reference25
DescriptionParameter
DirectoryStringSyntax
nsslapd-accesslog-logging-enabled: offExample
For access logging to be enabled, this attribute must be switched to on, and the
nsslapd-accesslog configuration attribute must have a valid path and parameter. Table 2-3
lists the four possible combinations of values for these two configuration attributes and their
outcome in terms of disabling or enabling of access logging.
Table 2-3 Attribute values for enabling or disabling access logging
Value of the
nsslapd-accesslog-logging-enabled
attribute
Value of the nsslapd-accesslog
attribute
Resulting logging state
on
filenameon
off
filenameoff
2.3.1.8 nsslapd-accesslog-logmaxdiskspace (Access log maximum disk space)
This attribute specifies the maximum amount of disk space in megabytes that the access logs are
allowed to consume. If this value is exceeded, the oldest access log is deleted.
When setting a maximum disk space, consider the total number of log files that can be created
due to log file rotation. Also, remember that there are three different log files (access log, audit
log, and error log) maintained by the Directory Server, each of which consumes disk space.
Compare these considerations to the total amount of disk space for the access log.
DescriptionParameter
cn=configEntryDN
Valid Range
-1 | 1 to the maximum 32-bit integer value (2147483647), where a value of -1 means that the
disk space allowed to the access log is unlimited in size.
500Default Value
IntegerSyntax
Disabledempty string
Enabled
Disabledempty string
Disabled
nsslapd-accesslog-logmaxdiskspace: 200Example
2.3.1.9 nsslapd-accesslog-logminfreediskspace (Access log minimum free disk space)
This attribute sets the minimum allowed free disk space in megabytes. When the amount of free
disk space falls below the value specified on this attribute, the oldest access logs are deleted until
enough disk space is freed to satisfy this attribute.
DescriptionParameter
cn=configEntryDN
1 to the maximum 32-bit integer value (2147483647)Valid Range
This attribute sets whether access log rotation is to be synchronized with a particular time of the
day. Synchronizing log rotation this way can generate log files at a specified time during a day,
such as midnight to midnight every day. This makes analysis of the log files much easier because
they then map directly to the calendar.
For access log rotation to be synchronized with time-of-day, this attribute must be enabled with
the nsslapd-accesslog-logrotationsynchour and
nsslapd-accesslog-logrotationsyncmin attribute values set to the hour and minute of
the day for rotating log files.
For example, to rotate access log files every day at midnight, enable this attribute by setting its
value to on, then set the values of the nsslapd-accesslog-logrotationsynchour and
nsslapd-accesslog-logrotationsyncmin attributes to 0.
This attribute sets the hour of the day for rotating access logs. This attribute must be used in
conjunction with nsslapd-accesslog-logrotationsync-enabled and
nsslapd-accesslog-logrotationsyncmin attributes.
This attribute sets the minute of the day for rotating access logs. This attribute must be used in
conjunction with nsslapd-accesslog-logrotationsync-enabled and
nsslapd-accesslog-logrotationsynchour attributes.
DescriptionParameter
cn=configEntry DN
0 through 59Valid Range
0Default Value
IntegerSyntax
nsslapd-accesslog-logrotationsyncmin: 30Example
2.3 Core server configuration attributes reference27
This attribute sets the time between access log file rotations. The access log is rotated when this
time interval is up, regardless of the current size of the access log. This attribute supplies only
the number of units. The units (day, week, month, and so forth) are given by the
nsslapd-accesslog-logrotationtimeunit attribute.
Although it is not recommended for performance reasons to specify no log rotation because the
log grows indefinitely, there are two ways of specifying this. Either set the
nsslapd-accesslog-maxlogsperdir attribute value to 1 or set the
nsslapd-accesslog-logrotationtime attribute to -1. The server checks the
nsslapd-accesslog-maxlogsperdir attribute first,and, if this attribute value islarger than
1, the server then checks the nsslapd-accesslog-logrotationtime attribute. See
“nsslapd-accesslog-maxlogsperdir (Access log maximum number of log files)” for more
information.
DescriptionParameter
Entry DN
Valid Range
cn=config
-1 | 1 to the maximum 32-bit integer value (2147483647), where a value of -1 means that the
time between access log file rotation is unlimited.
1Default Value
IntegerSyntax
nsslapd-accesslog-logrotationtime: 100Example
2.3.1.14 nsslapd-accesslog-logrotationtimeunit (Access log rotation time unit)
This attribute sets the units for the nsslapd-accesslog-logrotationtime attribute.
2.3.1.15 nsslapd-accesslog-maxlogsize (Access log maximum log size)
This attribute sets the maximum access log size in megabytes. When this value is reached, the
access log is rotated. That means the server starts writing log information to a new log file. If the
nsslapd-accesslog-maxlogsperdir attribute is set to 1, the server ignores this attribute.
When setting a maximum log size, consider the total number of log files that can be created due
to log file rotation. Also, remember that there are three different log files (access log, audit log,
and error log) maintained by the Directory Server, each of which consumes disk space. Compare
these considerations to the total amount of disk space for the access log.
DescriptionParameter
cn=configEntry DN
Valid Range
28Core server configuration reference
-1 | 1 to the maximum 32-bit integer value (2147483647), where a value of -1 means the log
file is unlimited in size.
100DefaultValue
DescriptionParameter
IntegerSyntax
nsslapd-accesslog-maxlogsize: 100Example
2.3.1.16 nsslapd-accesslog-maxlogsperdir (Access log maximum number of log files)
This attribute sets the total number of access logs that can be contained in the directory where
the access log is stored. Each time the access log is rotated, a new log file is created. When the
number of files contained in the access log directory exceeds the value stored in this attribute,
then the oldest version of the log file is deleted.
NOTE:For performance reasons, HP recommends not setting this value to 1 because the server
does not rotate the log, and it grows indefinitely.
If the value for this attribute is higher than 1, then check the
nsslapd-accesslog-logrotationtime attribute to establish whether log rotationis specified.
If the nsslapd-accesslog-logrotationtime attribute has a value of -1, then there is no
log rotation. See “nsslapd-accesslog-logrotationtime (Access log rotation time)” for more
information.
DescriptionParameter
Entry DN
cn=config
1 to the maximum 32-bit integer value (2147483647)Valid Range
This attribute sets the access mode or file permission with which access log files are to be created.
The valid values are any combination of 000 to 777 (these mirror the numbered or absolute
UNIX file permissions). The value must be a 3-digit number, the digits varying from 0 through
7:
0
1
2
3
None
Execute only
Write only
Write and execute
DescriptionDigitDescriptionDigit
4
5
6
7
Read only
Read and execute
Read and write
Read, write, and execute
In the 3-digit number, the first digitrepresents the owner's permissions, the second digit represents
the group's permissions, and the third digit represents everyone's permissions. When changing
the default value, remember that 000 prevents access to the logs and that allowing write
permissions to everyone can result in the logs being overwritten or deleted by anyone.
The newly configured access mode takes effect immediately for any open log file, as well as for
any log files that are created subsequently.
2.3 Core server configuration attributes reference29
NOTE:
Any umask set for the runtime user of the Directory Server causes the effective mode to be more
restrictive.
DescriptionParameter
Entry DN
cn=config
000 through 777ValidRange
600Default Value
IntegerSyntax
nsslapd-accesslog-mode: 600Example
2.3.1.18 nsslapd-attribute-name-exceptions
This attribute allows non-standard characters in attribute names to be used for backwards
compatibility with older servers, such as "_" in schema-defined attributes.
DescriptionParameter
Entry DN
Valid Values
cn=config
on or off
offDefault Value
DirectoryStringSyntax
nsslapd-attribute-name-exceptions: onExample
2.3.1.19 nsslapd-auditlog (Audit log)
This attribute sets the path and file name of the log used to record changes made to each database.
For audit logging to be enabled, this attribute must have a valid path and parameter, and the
nsslapd-auditlog-logging-enabled configuration attribute must be switched to on.
Table 2-4 lists the four possible combinations of values for these two configuration attributes
and their outcome in terms of disabling or enabling of audit logging.
Table 2-4 Attribute values for enabling or disabling audit logging
Value of the
nsslapd-auditlog-logging-enabled
Resulting logging state
Disabled
Enabled
empty string
AttributeValue of the nsslapd-auditlog Attribute
on
onfilename
30Core server configuration reference
Loading...
+ 242 hidden pages
You need points to download manuals.
1 point = 1 manual.
You can buy points or you can get point for every manual you upload.