Red Hat Directory Server B.08.00 for HP-UX Release Notes and Supplemental Instructions HP-UX 11i v1, HP-UX 11i v2, and HP-UX 11i v3 HP Part Number: J4258-90068 Published: November 2008 Edition: 1.
© Copyright 2008 Hewlett-Packard Development Company, L.P. Confidential computer software. Valid license from HP required for possession, use or copying. Consistent with FAR 12.211 and 12.212, Commercial Computer Software, Computer Software Documentation, and Technical Data for Commercial Items are licensed to the U.S. Government under vendor's standard commercial license. The information contained herein is subject to change without notice.
Important Licensing Requirements IMPORTANT: Red Hat Directory Server product licensing requirements have been changed. Please read the following licensing terms and conditions.
Table of Contents 1 Release Notes for Red Hat Directory Server B.08.00................................................9 New Features in Red Hat Directory Server 8.0......................................................................................9 Differences Between Red Hat Directory Server 7.1 and Red Hat Directory Server 8.0........................11 Documentation......................................................................................................................................
Tips for Using Red Hat Directory Server 8.0........................................................................................31 Importing LDIF Files.......................................................................................................................31 Directory Server Console Import...............................................................................................32 The ldapmodify -a Command .................................................................................
Attributes Added in Version 8.0......................................................................................................67 C Manually Migrating a Directory Server to a System with a Different Host Name................................................................................................................................
List of Tables 1-1 1-2 2-1 8 Documentation for Red Hat Directory Server 8.0.........................................................................12 Red Hat Directory Paths and HP-UX Directory Paths..................................................................12 Red Hat Directory Server 8.0 Files and Directories.......................................................................
1 Release Notes for Red Hat Directory Server B.08.00 Red Hat Directory Server 8.0 for HP-UX provides an industry standard centralized directory service based on the Lightweight Directory Access Protocol (LDAP). You can use Red Hat Directory Server 8.0 to build an intranet or extranet directory service.
structure that conforms to the file hierarchy system used for other HP-UX products. This structure uses different directories for configuration data, server application data, and binary files. This structure enables you to use multiple file systems to store product data and files. • Improved Password Quality Policy Management and Enforcement Red Hat Directory Server 8.0 enhances password syntax checking to enforce its password policies.
Differences Between Red Hat Directory Server 7.1 and Red Hat Directory Server 8.0 The following list describes the differences between HP Red Hat Directory Server 7.1 and Red Hat Directory Server 8.0: • Red Hat Directory Server 8.0 does not support the following features: — IM Presence Information — DSML Gateway — Phonebook and Gateway web applications • • Red Hat Directory Server 7.1 uses a proprietary web server for directory administration server components. Red Hat Directory Server 8.
Documentation Table 1-1 lists documentation available for Red Hat Directory Server 8.0: Table 1-1 Documentation for Red Hat Directory Server 8.0 Title Description README.hp file Provides Red Hat Directory Server 8.0 product release information. It is located in the /opt/dirsrv directory. Red Hat Directory Server B.08.00 for Describes new information about the Red Hat Directory Server 8.
Known Problems Fixed in Red Hat Directory Server 8.0 Red Hat Directory Server 8.0 corrects the following Red Hat Directory Server 7.1 problems: • • • • • • • • • • • • • • Existing entries in subfolders were not synchronized when Windows Sync was initiated. The synchronization has been fixed so that the search scope is for the entire subtree, not just one level.
Workaround Use the certutil command-line utility to create a certificate request, or use the Certificate Request Wizard with the following workaround: 1. 2. 3. 4. In the Requestor Information dialog box, enter the attribute values for the subject Distinguished Name (DN). Select Show DN. The Wizard opens a window that displays the DN. Remove the double quotes that enclose each attribute value. Select Next to continue creating the certificate request. NOTE: The attribute values cannot contain commas.
Workaround If you use the Red Hat Administration Server on an HP-UX 11i v1 system, move the Apache NSPR library files to an alternate location. For more information, see “NSPR Compatibility Problem on HP-UX 11i v1 Systems” (page 19). • The nssldap-db-transaction-logging is deprecated The database configuration option nsslapd-db-transaction-logging is deprecated. Disabling transaction logging can cause runtime database corruption. This option remains only for experimental purposes.
NOTE: If you are importing or exporting an LDIF on the local system, you can specify the file using a relative path. • Console cannot find the CRL file When using the console to install a CRL, the console returns an error if the CRL is placed in the /etc/opt/dirsrv/slapd-instance directory. Workaround Place the CRL in the administration server directory, /etc/opt/dirsrv/admin-serv. The console can locate the CRL file.
2 Installing Red Hat Directory Server 8.0 This chapter contains information that supplements the Red Hat Directory 8.0 Server Installation Guide for installing the product on HP-UX. This chapter addresses the following topics: • • • “Preparing for Red Hat Directory Server 8.0 Installation” (page 17) “Using swinstall to Install Red Hat Directory Server 8.0” (page 22) “Verifying Installation” (page 23) Preparing for Red Hat Directory Server 8.
Disk Space Requirements The disk space requirements for the /opt/dirsrv, /etc/opt/dirsrv/ and /var/opt/ dirsrv directories are as follows: • /opt/dirsrv The initial product installation requires 115 MB of space in /opt/dirsrv for executables, libraries, scripts, and other related data. Each Directory Server instance created requires 1 MB of space in /opt/dirsrv. • /etc/opt/dirsrv The initial product installation requires 0.5 MB of space in /etc/opt/dirsrv for shared configuration files.
You can download patches and Quality Patch bundles from the HP IT Resource Center patch database: http://itrc.hp.com/service/home/home.do Select patch database under maintenance and support (hp products). Additional Software Requirements This section lists additional software modules required for Red Hat Directory Server 8.0.
Procedures for Resolving JRE Dependency HP recommends that you use the following procedures to install Red Hat Directory Server 8.0 and resolve the JRE software dependency: • If a version of JRE 1.5 is installed on the system and the version is equal to or greater than 1.5.0.11, then you can skip the JRE installation requirement. To check if the correct version of JRE 1.5 is installed on the system, use the following command: /usr/bin/swlist -l product | grep Java15JRE • If the JRE 1.
http://software.hp.com In the Search field enter OpenSSL11i. Console Online Help Requirement The system must have a Firefox or Mozilla web browser installed to use the online help feature in the Administration Console. The Firefox browser is included with most HP-UX OE releases and is available from the HP-UX Firefox website: http://www.hp.
If you use the default values for these parameters, set the value for the maxdsiz or maxdsiz_64bit parameter to at least 25 MB. This assumes that the Directory Server processes are tuned to use a single heap arena. for more information, see“Heap Arenas” (page 30). For information about setting the Directory Server cache sizes, see “Tuning Database Performance ” (page 29).
• • /var/opt/dirsrv /etc/opt/dirsrv-admin Table 2-1 lists the files and directories installed with Red Hat Directory Server 8.0: Table 2-1 Red Hat Directory Server 8.
3 Setting Up Red Hat Directory Server 8.0 This chapter describes how to set up and configure Red Hat Directory Server 8.0. It addresses the following topics: • “Overview” (page 25) — — • • “IP Address and DNS Requirements” (page 25) “Keeping a Response File (-k Option)” (page 26) “Running the setup-ds-admin.pl or setup-ds.
Keeping a Response File (-k Option) The setup-ds-admin and setup-ds.pl scripts support the -k option to keep a copy of your responses in a file named setupXXXXX.inf (where each X is a random character). You can use this file to set up additional Directory Server instances with the same configuration parameters. WARNING! Keeping the setupXXXXX.inf file is a security risk because it contains passwords stored in clear text.
o=NetscapeRoot directory tree) and is the first Directory Server instance configured in an administration domain. NOTE: If the server you are installing is not the Configuration Directory Server, a Configuration Directory Server must be configured and available. Answer the prompts about the existing Configuration Directory Server as follows: a. Configuration Directory Server URL [local_ldap_url]: Specify the URL for the Configuration Directory server.
a. Configuration directory server administrator ID: Enter the user name you log in with when you authenticate to the console with full privileges. The default is admin. b. Password: Establish a password for the Configuration Directory Administrator. Enter the same password when the script prompts you to confirm it. c. Administration domain: Enter the Configuration Directory Server DNS domain. The default is the domain configured for the local host in the /etc/resolv.conf file. 9.
• • “Configuring the Autostart Option” (page 29) “Tuning Database Performance ” (page 29) Configuring the Autostart Option By default, Red Hat Directory Server 8.0 configures the autostart options for the Directory Server and Administration Server daemons so they automatically start at system startup. If SSL is enabled for a Directory Server instance, the autostart feature skips that instance because the daemon prompts for the SSL key password.
(nsslapd-dbcachesize) + (nsslapd-cachememsize) <= maxdsiz (in bytes) where nsslapd-dbcachesize nsslapd-cachememsize maxdsiz Specifies the database cache size available for storing database indexes and database related data. Specifies the maximum amount of memory allowed in cache memory to store the cached database entries. Specifies the maximum data segment size for a process (the kernel parameter maxdsiz or maxdsiz-64bit).
4 Supplemental Information for Administering Red Hat Directory Server 8.0 This chapter contains information that supplements the Red Hat Directory 8.0 Server Installation Guide for configuring, administering, and troubleshooting the product on HP-UX. It addresses the following topics: • • • • “Stopping and Restarting the Directory Server” (page 31) “Stopping and Restarting the Administration Server” (page 31) “Tips for Using Red Hat Directory Server 8.
information on LDIF files, see Chapter 4 "Populating Directory Databases" in the Red Hat Directory Server 8.0 Administrator's Guide. You can use the following methods to import LDIF files: • The import feature in the Directory Server Console • The ldapmodify -a command-line utility • The ldif2db.pl script for fast online import • The ldif2db command-line script • The ldif2ldap command-line script The ldapmodify tool is located in the /opt/dirsrv/bin directory. The ldif2db.
Troubleshooting This section describes problems you might encounter and how to resolve them. For more information, see the Red Hat Directory Server 8.0 Installation Guide. Server Cannot Allocate Import Cache for Replica Initialization The Directory Server allocates one import cache for each online replica initialization operation. If you configure a large import cache size it is possible to configure an import cache size that is so large that the server cannot allocate the cache for replica initialization.
supportedExtension: 2.16.840.1.113730.3.5.4 supportedExtension: 1.3.6.1.4.1.4203.1.11.1 supportedControl: 2.16.840.1.113730.3.4.2 supportedControl: 2.16.840.1.113730.3.4.3 supportedControl: 2.16.840.1.113730.3.4.4 supportedControl: 2.16.840.1.113730.3.4.5 supportedControl: 1.2.840.113556.1.4.473 supportedControl: 2.16.840.1.113730.3.4.9 supportedControl: 2.16.840.1.113730.3.4.16 supportedControl: 2.16.840.1.113730.3.4.15 supportedControl: 2.16.840.1.113730.3.4.17 supportedControl: 2.16.840.1.113730.3.4.
5 Migrating to Red Hat Directory Server 8.0 This chapter describes how to migrate a Netscape Directory Server version 6.11 or 6.21 or a Red Hat Directory Server 7.1 to Red Hat Directory Server 8.0. HP does not support migration from Netscape Directory Server 6.02 or earlier versions, such as 3.x, 4.x, 6.02, or iPlanet Directory Server 5.0. For additional information, see Chapter 8, "Migrating From Previous Versions," in the Red Hat Directory Server 8.
The migration tools are not interactive and provide the following features: • • • No prompts appear, and you are not required to enter any information or approve any step in the migration process. The script displays the migration status after the migration completes. The migration tools copy the Directory Server information and settings from the existing Directory Server instance to the new instance. The existing Directory Server instance is not modified or destroyed.
For example, the following command creates the tar file server7.tar for instance1 and instance2 : tar cf /tmp/bak/server7.tar \ slapd-instance1/config \ slapd-instance2/config \ slapd-instance1/schema \ slapd-instance2/schema \ alias \ admin-serv/config \ shared/config 3. If you are migrating from Red Hat Directory Server 7.1 to Red Hat Directory Server 8.0, skip this step. Otherwise, if you are migrating Directory Server 6.11 or 6.21 (32-bit architecture) to Directory Server 8.
5. Verify that the Red Hat Directory Server 8.0 schema does not conflict with your current schema usage. Red Hat Directory Server 8.0 adds new schema elements, such as those used for the new password policy features. This new schema might conflict with schema already used in your current directories. See Appendix B (page 55) for a list of schema differences between Red Hat Directory Server 8.0 and previous versions.
NOTE: The configuration administrator is not the same as the directory manager (cn=Directory Manager). The configuration administrator (by default, the user admin) manages the server instances in the administration domain and has the DN uid=admin, ou=Administrators, ou=TopologyManagement, o=NetscapeRoot. Migrating to Red Hat Directory Server 8.
4. Run the migration script as the root user: • To migrate from Directory Server 6.11 or 6.21 to 8.0, select one of the following options. NOTE: You must have the LDIF files created for your legacy directories. See “Preparing for Migration” (page 36). — To migrate all Netscape Directory Server 6.11 or 6.21 instances and the Administration Server to Red Hat Directory Server 8.0, use the following command sequence: cd /opt/dirsrv/sbin ./migrate-ds-admin.
cd /opt/dirsrv/sbin ./migrate-ds.pl --oldsroot /var/opt/netscape/server7 \ --instance slapd-instance The migration script migrates the legacy Directory Server and creates Red Hat Directory Server 8.0 Directory Servers using the configuration information from the legacy Directory Server instances. If you used the migrate-ds-admin.pl script, the script also creates a new Administration Server. The migration script also starts the new Directory Server instances and the Administration Server.
Migration from Netscape Directory Server 6.02 and earlier is not supported. For additional information about migration, see Chapter 8, "Migrating From Previous Versions" in the Red Hat Directory Server 8.0 Installation Guide before you start the migration process. IMPORTANT: A large number of configuration parameters are based on the Directory Server's host name including Console, replication, TLS/SSL. The migration scripts cannot change the host name used by the Directory Server and Administration Server.
IMPORTANT: The db_name portion of the LDIF file name must match the database name, and this name is case sensitive. For example, the LDIF file name for the NetscapeRoot database must be NetscapeRoot.ldif. Be sure to specify the -r option. This option causes the migration tool to migrate replica state information. If you do not specify the -r option, and you must re-initialize replicas after the migration completes. 4. 5.
8. On the HP-UX 11i v2 or v3 HP Integrity system, uncompress the legacy directory Server installation directory files you transferred from the legacy Directory Server. For example, the following commands uncompress the file, legacydir.tar: cd /tmp/oldserver tar -xvf legacydir.tar Running the Migration Tool After transferring and extracting the files from the legacydir.tar file, complete the following steps to run the migration tool: 1. 2. Use swinstall to install Red Hat Directory Server 8.
NOTE: The configuration administrator is not the same as the directory manager (cn=Directory Manager). The configuration administrator (by default, the user admin) manages the server instances in the administration domain and has the DN uid=admin, ou=Administrators, ou=TopologyManagement, o=NetscapeRoot. Migrating a Directory Server on an HP 9000 System to Red Hat Directory Server 8.
3. Run the appropriate migration script as the root user. For the --oldsroot argument, specify the directory that contains the uncompressed legacy Directory Server tar file contents, such as /tmp/oldserver. • To migrate from Netscape Directory Server 6.11 or 6.21, select one of the following options: — To migrate all Netscape Directory Server 6.11 or 6.21 instances and the Administration Server to Red Hat Directory Server 8.0, use the following command sequence: cd /opt/dirsrv/sbin ./migrate-ds-admin.
cd /opt/dirsrv/sbin ./migrate-ds-admin.pl --oldsroot oldserver_datadir \ --actualsroot /var/opt/netscape/server7 \ --instance slapd-instance --cross The migration script migrates the legacy Directory Server and creates Red Hat Directory Server 8.0 Directory Servers using the configuration information from the legacy Directory Server instances. If you used the migrate-ds-admin.pl script, the script also creates new a Administration Server.
CAUTION: A password file contains the password for the SSL private key token in clear text and is a security risk. If you create a password file, HP recommends that you delete it after you complete the migration. NOTE: If the server host or CA certificate is expired, the server cannot start during the migration process, and the migration fails. Although previous Directory Server versions can operate with expired certificates, Red Hat Directory Server 8.
Creating a Password File for the SSL Private Key Token Use the following procedure to create a password file for the SSL private key token for the legacy Directory Server. The migration script creates a copy of the file and installs it in the Red Hat Directory Server 8.0 directory /etc/opt/dirsrv/slapd-instance. 1. 2. 3. Log in as root. Stop the legacy Directory Server (the Directory Server that you are going to migrate) if you have not stopped it.
Server 6.11 or 6.21 After Migration ” (page 50) or “Removing Red Hat Directory Server 7.1 After Migration” (page 50). If you migrated a secure Directory Server, re-enable SSL security if needed or delete the password file for the SSL private key token. See “Re-enabling SSL Security” (page 48) and “Deleting the Password File for the SSL Private Key Token” (page 49). Removing Netscape Directory Server 6.11 or 6.21 After Migration To remove Netscape Directory Server 6.11 or 6.
NOTE: 1. The commands in this procedure use the Bourne shell scripting language. Shut down the administration server: cd /opt/dirsrv/sbin ./stop-ds-admin NOTE: 2. Remove the data for the Administration Server: cd rm rm rm rm rm rm 3. The stop-ds-admin utility might report that the server is not running. /etc/opt/dirsrv/admin-serv -f admpw -f adm.conf -f cert8.db -f key3.db -f secmod.db -f local.conf Shut down the any newly created servers: cd /opt/dirsrv for name in slapd-* ; do .
A Migration Tools This appendix provides information about the major options and arguments that the migrate-ds-admin.pl and migrate-ds.pl tools support. Major Options The migrate-ds-admin.pl and migrate-ds.pl tools support the following major options: --oldsroot -o Required. If you migrate the legacy Directory Server 6.11, 6.21 or 7.1 to Directory Server 8.0 on the same system, this option specifies the path to the installation directory of the legacy Directory Server 6.11, 6.21 or 7.
--logfile name -l name Optional. Specifies a log file to log the migration messages. If this option is not set, the migration information is written to a temporary file, /tmp/migratexxxx.log. To disable logging, set this option to /dev/null. --cross -c or -x Optional. This is used when the source system is a different architecture than the destination system. When you migrate from one system to another or migrate from one platform to another platform, you must perform cross-platform migration.
B Schema Changes Red Hat Directory Server versions 7.1 and 8.0 include changes to the LDAP schema. Red Hat Directory Server 8.0 removes multiple rarely used and application-specific schema definitions and adds new schema elements, such as those used for the new password policy features. This appendix lists schema changes introduced in Red Hat Directory Server versions 7.1 and 8.0. Red Hat Directory Server 7.1 Schema Changes This section lists differences between Red Hat Directory Server 7.
Object Classes Removed in Version 8.
nsmsgCfgmtaprogdeliver nsmsgCfgmtarouter nsmsgCfgmtasmtpdeliver nsmsgCfgmtaunixdeliver nsmsgCfgpartition nsmsgCfgpop nsmsgCfgpublic nsmsgCfgreport nsmsgCfgscript nsmsgCfgservice nsmsgCfgsnmp nsmsgCfgstore nsmsgCfguser nsmsgPipeProgram nswcalUser personalInterestProfile Attributes Removed in Version 8.
icsSubscribed icsTimezone inetResourceStatus mgmanAllowSubscribe mgmanDenySubscribe mgmanGConfAdmin mgmanGConfDefaultInheritance mgmanGConfGroupCreationUser mgmanGConfGroupDomains mgmanGConfGroupTemplate mgmanGConfKey mgmanGConfNewGroupParent mgmanGConfRemoteUserParent mgmanGConfSearchAttribute mgmanGConfSearchBase mgmanGConfSearchGroupUser mgmanGConfSearchRelationship mgmanGConfSearchTreeNode mgmanGConfSortAttributeDirMembers mgmanGConfSortAttributeGroupMembers mgmanGroupKey mgmanGroupStat mgmanHidden mgma
nsBCMimeAllowRemove nsBCMimeType nsBCNoProxiesOn nsBCOfflinePromptSynchOnExit nsBCOfflineSendUnsentMessages nsBCOfflineStartupState nsBCProxyAutoConfigUrl nsBCProxyFtp nsBCProxyGopher nsBCProxyHttp nsBCProxySocks nsBCProxySsl nsBCProxyType nsBCProxyWais nsBCRelatedAutoload nsBCRelatedDisabledForDomains nsBCRelatedEnabled nsBCStartupBrowser nsBCStartupCalendar nsBCStartupEditor nsBCStartupHomePage nsBCStartupMail nsBCStartupPage nsBCUnderlineAnchors nsBCUseDocumentColors nsBCUseDocumentFonts nsBCVisitedColor
nsCalOperatingPrefs nsCalOrgUnit2 nsCalOrgUnit3 nsCalOrgUnit4 nsCalPasswordRequired nsCalPrmd nsCalRefreshPrefs nsCalResourceCapacity nsCalResourceNumber nsCalServerVersion nsCalSysopCanWritePassword nsCalTimezone nsCalXItemId nsDADomain nsDefaultMaxDeptSize nsLIData nsLIElementType nsLIPrefs nsLIProfileName nsLIPtrURL nsLIServerType nsLIVersion nsMCAddrBookLastnameFirst nsMCAddrBookLdapDisabled nsMCAllowAtSignInUserName nsMCAllowAtSignInUserName1 nsMCAltMailDll nsMCAuthLogin nsMCAutoCompleteEnabledServerNa
nsMCNewsRemoveBodiesByAge nsMCNewsRemoveBodiesDays nsMCNewsTimeout nsMCPlaySound nsMCPop3GetsNewMail nsMCPopServer nsMCPopServerProperties nsMCPromptPurgeThreshold nsMCPurgeThreshold nsMCQuotedSize nsMCQuotedStyle nsMCReceiptRequestHeaderType nsMCRememberSelectedMessage nsMCReplyOnTop nsMCRequestReturnReceipt nsMCReuseMessageWindow nsMCSearchServer nsMCSearchSubFolders nsMCShowHeaders nsMCSkipDirectoryIfLocalMatchFound nsMCSmtpServer nsMCSmtpUseSSL nsMCSmtpUserName nsMCSpellCheckBeforeSend nsMCStrictlyMime
nsMcdUserAgent nsMcdXAnimationFile nsNumDepts nsNumDomains nsNumMailLists nsNumUsers nsPrefMap nsSearchFilter nsaclrole nscreator nsdaCapability nsdaModifiableBy nsflags nsmsgAccounturl nsmsgAdddeliveredto nsmsgAddheaders nsmsgAdmins nsmsgAlias nsmsgAllowadminproxy nsmsgAllowanonymouslogin nsmsgAllowbarelf nsmsgAllowbdat nsmsgAllowehlo nsmsgAllowetrn nsmsgAllowexpn nsmsgAllowhelp nsmsgAllowonex nsmsgAllowsize nsmsgAllowverb nsmsgAllowvrfy nsmsgAltqueues nsmsgAlwaysqueue nsmsgAuthcachesize nsmsgAuthcachettl
nsmsgDnsresolveclient nsmsgDocanonicalize nsmsgDoclientdnslookup nsmsgDodsn nsmsgDoetrn nsmsgDomainallowed nsmsgDomainlangtable nsmsgDomainname nsmsgDomainnotallowed nsmsgDomainsecurity nsmsgDorewritefromusingauth nsmsgDorewritesenderusingauth nsmsgEnable nsmsgEnablesslport nsmsgEnveloperewritemethod nsmsgExclusive nsmsgExpirestart nsmsgExpirytime nsmsgExternalmxserverip nsmsgExtrauserldapattrs nsmsgFallbacksearchmethod nsmsgFilemode nsmsgFilterurl nsmsgFlushinterval nsmsgFolderpattern nsmsgFoldersizebytes
nsmsgMaxlogfilesize nsmsgMaxlogsize nsmsgMaxmessagesize nsmsgMaxmtahops nsmsgMaxpostsize nsmsgMaxqueuetime nsmsgMaxruncount nsmsgMaxruncountdeferred nsmsgMaxscriptsize nsmsgMaxsessions nsmsgMaxstateobjectsize nsmsgMaxthreads nsmsgMessagecount nsmsgMessagedays nsmsgMessagehostname nsmsgMessagesize nsmsgMessagesizedays nsmsgMinfreediskspace nsmsgMinruncount nsmsgMsgalarmdescription nsmsgMsgalarmnoticehost nsmsgMsgalarmnoticeport nsmsgMsgalarmnoticercpt nsmsgMsgalarmnoticesender nsmsgMsgalarmnoticetemplate nsm
nsmsgReadtimeout nsmsgRenotifyinterval nsmsgRequirecrlf nsmsgReserved0 nsmsgReserved1 nsmsgReserved2 nsmsgReserved3 nsmsgReserved4 nsmsgReserved5 nsmsgReserved6 nsmsgReserved7 nsmsgReserved8 nsmsgReserved9 nsmsgResourcetimeout nsmsgRewritetocc nsmsgRolloverdelta nsmsgRolloversize nsmsgRollovertime nsmsgRoutingattribute nsmsgRoutstripimapfolders nsmsgServiceadmingroupdn nsmsgSessiontimeout nsmsgShellpath nsmsgSitelanguage nsmsgSmtphost nsmsgSmtpport nsmsgSmtprewritestyle nsmsgSourceurl nsmsgSpooldir nsmsgSsl
piphour pipidstcount pipirlist pipiroption piplastcount pipmaxhits pipmedium pipnotify pipprivilege pippwp pipreservedces1 pipreservedces2 pipreservedces3 pipreservedcis1 pipreservedcis2 pipreservedcis3 pipreservedcis4 pipreservedcis5 pipreservedcis6 pipresultset pipsortorder pipstatus pipstcategory pipstformat pipstfrequency pipsthour pipstid pipstinterest pipstirlist pipstiroption pipstlastcount pipstmaxhits pipstmedium pipstname pipstprivacy pipstquery pipstresultset pipstsortorder pipststatus pipstcateg
pipuniqueid pipusertype url Object Classes Added in Version 8.0 None. Attributes Added in Version 8.0 pamIDMapMethod passwordMaxRepeats passwordMin8bit passwordMinAlphas passwordMinCategories passwordMinDigits passwordMinLowers passwordMinSpecials passwordMinTokenLength passwordMinUppers Red Hat Directory Server 8.
C Manually Migrating a Directory Server to a System with a Different Host Name To use the automated procedure described in “Migrating a Directory Server on an HP 9000 System to Red Hat Directory Server 8.0 on a Different System” (page 41), you must assign the source host name to the target system. If you want to migrate a Directory Server to a target system with a different host name, you can use the manual procedure described in this appendix.
--actualsroot /var/opt/netscape/server7 \ --instance slapd-instance 6. 70 Use the register-ds-admin.pl script to register the migrated Directory Server instances with the Configuration Directory Server.
