Содержащиеся вНайти другие документыРесурсы поддержки |  Загрузить это руководство в формате PDF (3630 КБ)
Administration Commandsdpadm(1M)NAME | Synopsis | Description | SUBCOMMANDS | GLOBAL OPTIONS | SUBCOMMAND OPTIONS | SUBCOMMAND OPERANDS | Exit Status | Examples | Attributes | See Also NAME
Synopsisinstall-path/dps6/bin/dpadm [subcommand] [global-options] [subcommand-options] [subcommand-operands] DescriptionThe dpadm command is the administration command for the Directory Proxy Server. Use the dpadm command with one of the subcommands described in this man page. SUBCOMMANDS
The following subcommands are supported: GLOBAL OPTIONS
The following options are global, and are applicable to all commands and subcommands. SUBCOMMAND OPTIONS
The following options are applicable to the subcommands where they are specified. SUBCOMMAND OPERANDS
The following operands are supported: Exit StatusExamplesThe following examples show how the dpadm command is used. Example 1 Creating a Directory Proxy Server InstanceThe following example shows how to create a Directory Proxy Server instance.
Example 2 Starting a Directory Proxy Server InstanceThe following example shows how to start a Directory Proxy Server instance.
Example 3 Getting Information about a Directory Proxy Server InstanceThe following example shows how to get information about a Directory Proxy Server instance.
AttributesSee attributes(5) for descriptions of the following attributes:
See AlsoDPS 6.2 Last Revised April 16, 2007NAME | Synopsis | Description | SUBCOMMANDS | GLOBAL OPTIONS | SUBCOMMAND OPTIONS | SUBCOMMAND OPERANDS | Exit Status | Examples | Attributes | See Also dpconf(1M)NAME | Synopsis | Description | SUBCOMMANDS | GLOBAL OPTIONS | SUBCOMMAND OPTIONS | SUBCOMMAND OPERANDS | Description | Exit Status | Examples | Attributes | See Also NAME
Synopsisinstall-path/dps6/bin/dpconf subcommand [global-options] [subcommand-options] [subcommand-operands] DescriptionThe dpconf command manages the configuration of Directory Proxy Server. An instance of Directory Proxy Server must be running in order for you to run the dpconf command. SUBCOMMANDS
The following subcommands are supported: GLOBAL OPTIONS
The following options are global to all commands and subcommands: SUBCOMMAND OPTIONS
The following options can be used with the subcommands: SUBCOMMAND OPERANDS
The following operands can be used with the subcommands: Description
Syntax values shown in lower case or partly in lower case are literal values. Those shown in upper case are syntax types, defined as follows: Exit StatusExamples
This section contains examples of how the dpconf command is used. Example 1 Getting Help With a SubcommandThis example shows how to get help for using a subcommand:
Example 2 Getting Information About PropertiesThis example shows how to get information about the properties of the resource limits policy. Example 3 Getting Properties for Access LogsThis example shows how to get the access log properties, specifying that the log-rotation-size property is quoted in bytes.
Example 4 Customizing Search LimitsThis example shows how to define customized limits for search operations, based on the search base and search scope. Example 5 Comparing Properties of Connection HandlersThis example shows how to view the properties of one connection handler and how to compare the properties of a set of connection handlers. AttributesSee attributes(5) for descriptions of the following attributes:
See Alsodpadm(1M), dsconf(1M), and dsadm(1M) NAME | Synopsis | Description | SUBCOMMANDS | GLOBAL OPTIONS | SUBCOMMAND OPTIONS | SUBCOMMAND OPERANDS | Description | Exit Status | Examples | Attributes | See Also dsadm(1M)NAME | Synopsis | Description | SUBCOMMANDS | GLOBAL OPTIONS | SUBCOMMAND OPTIONS | Operands | Exit Status | Examples | Attributes | See Also NAME
Synopsisinstall-path/ds6/bin/dsadm subcommand options DescriptionThe dsadm command is the local administration command for Directory Server instances. Use the dsadm command with any of the subcommands described in this man page. dsadm must be used while the server is stopped (except subcommands dsadm info, dsadm stop and dsadm restart). It must be run from the local machine where the server instance is located. This command must be run by the username that is the Operating System owner of the server instance, or by root. SUBCOMMANDS
The following subcommands are supported: GLOBAL OPTIONS
The following options are global, and are applicable to all commands and subcommands. SUBCOMMAND OPTIONS
The following options are applicable to the subcommands where they are specified. Operands
The following operands are supported: Exit StatusExamplesThe following examples show how the dsadm command is used. Example 1 Creating a Directory Server Instance
This command creates the server instance files in the directory /local/ds. The server instance is owned by the UNIX user who creates the command. In this example, the LDAP port is specified as 6389, and the secure port is specified as 6636. If you do not specify port numbers, the default port numbers 389 and 636 (for root user) or 1389 and 1636 (for not-root user) are used. If you do not specify port numbers and the default port numbers are already being used, the dsadm create command aborts. Example 2 Starting a Directory Server InstanceThe server instance path is /local/ds.
Example 3 Getting Information About a Directory Server instanceThis command shows information such as the owner, ports, and current state of the server instance. The instance path is /local/ds.
Example 4 Importing an LDIF FileImport an LDIF file, specifying that no user confirmation is required, and giving the suffix DN.
Example 5 Exporting an LDIF FileExport a suffix to an LDIF file.
This command shows all data in the suffix dc=example,dc=com, excluding data in the subsuffix ou=People,dc=example,dc=com Example 6 Backing Up a Directory Server InstanceThis command backs up the suffix data and the configuration data. The instance path is /local/ds and the archive directory is /local/dsbackup/20060722 .
Example 7 Regenerating Attribute IndexesTo regenerate the existing cn and uid indexes:
Example 8 Renewing a CertificateUse the following command to renew an existing server certificate with a new server certificate from your Certificate Authority.
AttributesSee attributes(5) for descriptions of the following attributes:
See AlsoDS 6.2 Last Revised April 16, 2007NAME | Synopsis | Description | SUBCOMMANDS | GLOBAL OPTIONS | SUBCOMMAND OPTIONS | Operands | Exit Status | Examples | Attributes | See Also dsccmon(1M)NAME | Synopsis | Description | SUBCOMMANDS | GLOBAL OPTIONS | SUBCOMMAND OPTIONS | Environment Variables | Exit Status | Attributes | See Also NAME
Synopsisinstall-path/dscc6/bin/dsccmon [subcommand] [options] DescriptionThe dsccmon command is used to monitor servers registered with Directory Service Control Center. Use the dsccmon command with the subcommands described in this man page. SUBCOMMANDS
The following subcommands are supported: GLOBAL OPTIONS
The following options apply to all commands and subcommands: SUBCOMMAND OPTIONS
The following options apply to the subcommands where they are specified: Environment Variables
The following environment variables are supported: Exit StatusAttributesSee attributes(5) for descriptions of the following attributes:
See AlsoDS 6.2 Last Revised May 23, 2006NAME | Synopsis | Description | SUBCOMMANDS | GLOBAL OPTIONS | SUBCOMMAND OPTIONS | Environment Variables | Exit Status | Attributes | See Also dsccreg(1M)NAME | Synopsis | Description | SUBCOMMANDS | GLOBAL OPTIONS | SUBCOMMAND OPTIONS | Operands | Environment Variables | Exit Status | Attributes | See Also NAME
Synopsisinstall-path/dscc6/bin/dsccreg [subcommand] [options] DescriptionThe dsccreg command is used to register server instances on the local system with Directory Service Control Center, which may be remote. Use the dsccreg command with the subcommands described in this man page. SUBCOMMANDS
The following subcommands are supported: GLOBAL OPTIONS
The following options apply to all commands and subcommands: SUBCOMMAND OPTIONS
The following options apply to the subcommands where they are specified: OperandsEnvironment Variables
The following environment variables are supported: Exit StatusAttributesSee attributes(5) for descriptions of the following attributes:
See AlsoDS 6.2 Last Revised May 24, 2006NAME | Synopsis | Description | SUBCOMMANDS | GLOBAL OPTIONS | SUBCOMMAND OPTIONS | Operands | Environment Variables | Exit Status | Attributes | See Also dsccsetup(1M)NAME | Synopsis | Description | SUBCOMMANDS | GLOBAL OPTIONS | SUBCOMMAND OPTIONS | Exit Status | Attributes | See Also NAME
Synopsisinstall-path/dscc6/bin/dsccsetup [subcommand] [options] DescriptionThe dsccsetup command is used to register Directory Service Control Center with Sun Java Web Console (DSCC), and to register local agents of the administration framework. Use the dsccsetup command with the subcommands described in this man page. SUBCOMMANDS
The following subcommands are supported: GLOBAL OPTIONS
The following options apply to all commands and subcommands: SUBCOMMAND OPTIONS
The following options apply to the subcommands where they are specified: Exit StatusAttributesSee attributes(5) for descriptions of the following attributes:
See Alsocacaoadm(1M), smcwebserver(1M) NAME | Synopsis | Description | SUBCOMMANDS | GLOBAL OPTIONS | SUBCOMMAND OPTIONS | Exit Status | Attributes | See Also dsconf(1M)NAME | Synopsis | Description | SUBCOMMANDS | GLOBAL OPTIONS | SUBCOMMAND OPTIONS | Operands | Description | EXIT STATUS | Examples | Attributes | See Also NAME
Synopsisinstall-path/ds6/bin/dsconf subcommand options DescriptionThe dsconf command manages Directory Server configuration. It enables you to modify the configuration entries in cn=config. The server must be running in order for you to run dsconf. SUBCOMMANDS
The following subcommands are supported: GLOBAL OPTIONS
The following options are global, and are applicable to all commands and subcommands. SUBCOMMAND OPTIONS
The following options are applicable to the subcommands where they are specified. Operands
The following operands are supported: Description
Syntax values shown in lower case or partly in lower case are literal values. Those shown in upper case are syntax types, defined as follows: EXIT STATUSExamples
The following examples show how the dsconf command is used. Example 1 Create a Suffix
In this example, non-default ports are specified. Check to see if the suffix has been created.
Example 2 Import LDIF Data into the Suffix
Example 3 Index an AttributeIn this example, the preferredLanguage attribute is going to be indexed. Example 4 Back Up the Directory Server Data
For complete backup procedures, see the Sun Java System Directory Server Enterprise Edition 6.2 Administration Guide. Example 5 Monitor and Change Cache Size for a SuffixExample 6 Export to LDIF While Using Filters
This example shows a command that: Example 7 Rotate the Access Log and Modify the Rotation Delay for the Access LogIf you have a log which is getting very large, you can rotate the log. Rotation backs up the existing log file and creates a fresh log file. In this example, the access log is rotated. Example 8 Configure Replication in a Two-Master TopologyThis procedure configures replication on a topology with two severs, and both are masters. Replication is configured first on one master, then on the second master. Master 1 is located on server1.example:1389. Master 2 is located on server2.example:2389. The replication agreements in both directions are now active and replication is running. AttributesSee attributes(5) for descriptions of the following attributes:
See AlsoDS 6.2 Last Revised April 12, 2007NAME | Synopsis | Description | SUBCOMMANDS | GLOBAL OPTIONS | SUBCOMMAND OPTIONS | Operands | Description | EXIT STATUS | Examples | Attributes | See Also dsee_deploy(1M)NAME | Synopsis | Description | SUBCOMMANDS | Options | Exit Status | Attributes | See Also NAME
Synopsis./dsee_deploy install -c component -i install_path [OPTIONS] install-path/dsee6/bin/dsee_deploy uninstall -c component -i install_path [OPTIONS] DescriptionThe dsee_deploy command installs Directory Server Enterprise Edition software from zip distributions rather than native packages, and registers server software with the Cacao common agent container to allow remote administration. The dsee_deploy command also removes registration information from the Cacao common agent container, and removes Directory Server Enterprise Edition software installed from the zip distribution. Software installed from a zip distribution does not require that you have super user or administrator access to the system. The software is self-contained and need not have dependencies outside the install path you choose. SUBCOMMANDS
The following subcommands are supported: Options
The following options are supported: Exit Status
The following exit values are returned: AttributesSee attributes(5) for descriptions of the following attributes:
See Alsocacaoadm(1M), unzip(1) NAME | Synopsis | Description | SUBCOMMANDS | Options | Exit Status | Attributes | See Also dsmig(1M)NAME | Synopsis | Description | SUBCOMMANDS | GLOBAL OPTIONS | SUBCOMMAND OPTIONS | SUBCOMMAND OPERANDS | Exit Status | Examples | Attributes | See Also NAME
Synopsisinstall-path/ds6/bin/dsmig subcommand [options] [operands] DescriptionThe dsmig command is the migration command for a single Directory Server instance. Use the dsmig command with any of the subcommands described in this man page. dsmig migrates a Directory Server 5.1 instance to a Directory Server 6.2 instance. dsmig must be run from the local machine on which the new instance will be located. If the new instance exists, migration subcommands are carried out on that instance. If the new instance does not exist, dsmig creates the new instance with the parameters specified in the global options. SUBCOMMANDS
The following subcommands are supported. GLOBAL OPTIONS
The following options are global, and are applicable to all commands and subcommands. SUBCOMMAND OPTIONS
The following options are applicable to the subcommands where they are specified. SUBCOMMAND OPERANDS
The following operands are applicable to the subcommands where they are specified. Exit StatusExamplesThe following examples show how the dsmig command is used. Example 1 Migrating the schema
This command migrates the schema from the old Directory Server instance to the new 6.0 instance. In this example, the LDAP port is specified as 6389, and the secure port is specified as 6636. If you do not specify port numbers, the default port numbers 389 and 636 (for root user) or 1389 and 1636 (for not-root user) are used. If you do not specify port numbers and the default port numbers are already being used, the dsmig command aborts. Example 2 Migrating the configuration
This command migrates the configuration from the old Directory Server instance to the new instance. In this example, configuration data for the “o=netscapeRoot“ suffix and replication configuration data are migrated. Example 3 Migrating the data
This command migrates the data from the old Directory Server instance to the new instance. In this example, the replication change logs are not migrated. The NetscapeRoot database is migrated. Example 4 Migrating everything in a single step
In this example, replication configuration data is not migrated. Data for the “o=netscapeRoot“ suffix is migrated. Example 5 Obtaining migration status information
AttributesSee attributes(5) for descriptions of the following attributes:
See AlsoDS 6.2 Last Revised June 18, 2007NAME | Synopsis | Description | SUBCOMMANDS | GLOBAL OPTIONS | SUBCOMMAND OPTIONS | SUBCOMMAND OPERANDS | Exit Status | Examples | Attributes | See Also dsrepair(1M)NAME | Synopsis | Description | SUBCOMMANDS | Options | Exit Status | Attributes NAME
Synopsisinstall-path/ds6/support_tools/bin/dsrepair subcommand [options] arguments DescriptionThe dsrepair command makes it possible to repair entries that prevent replication from preceeding normally. You must enable the replication repair plug-in to use the dsrepair command. Use the dsrepair command only under the supervision of qualified support personnel. The dsrepair command functions only in non-secure mode, with simple authentication. The dsrepair command is not available on Windows systems, though it can be run against a Directory Server instance on a Windows system. SUBCOMMANDS
The following subcommands are supported: Options
The following options are supported: Exit StatusAttributesSee attributes(5) for descriptions of the following attributes:
NAME | Synopsis | Description | SUBCOMMANDS | Options | Exit Status | Attributes idsktune(1M)NAME | Synopsis | Description | Options | Extended Description | Exit Status | Attributes NAME
Synopsis./idsktune [-q] [-D] [-v] [-c] [-i install-path] DescriptionThe idsktune command checks patch levels and kernel parameter settings for the system on which Directory Server or directory client applications run, making tuning recommendations as it performs the checks. Run the command as super user to obtain the widest range of tuning recommendations. The idsktune command is delivered next to the dsee_deploy command with zip distribution software only. The idsktune command suggests changes you make to the system, but does not itself make any changes. You must fix at least all ERROR conditions identified by the idsktune command. The idsktune command reports as missing all patches recommended at the time of release and not installed on the system, even patches for packages not installed on the system. Options
The idsktune command supports the following options. Extended Description
The idsktune command verifies and reports on the following settings depending on the underlying system. Tuning system settings, especially network stack settings, involves considering potentially not just directory applications and Directory Server, but also other applications running on the system and in the environment. In general, however, implementing the recommendations optimizes directory performance whether the system is dedicated to Directory Server or shared with other applications. Exit StatusThe idsktune command exits with status 0 if it completes successfully and no ERRORs are found. Otherwise, it exists with non-zero status. AttributesSee attributes(5) for descriptions of the following attributes:
NAME | Synopsis | Description | Options | Extended Description | Exit Status | Attributes ns-accountstatus(1M)NAME | Synopsis | Description | Options | Exit Status | Examples | Attributes | See Also NAME
Synopsis
install-path/ds6/bin/ns-accountstatus
[-D rootDN] {-w password | -w - | -j filename} [-p port]
[-h host] -I accountDN
DescriptionThe ns-accountstatus command shows whether the account corresponding to an entry is active. The command can also be used to show whether the accounts corresponding to a role are active. Options
The following options are supported: Exit Status
The following exit values are returned: ExamplesThe examples in this section use sample data from the Example-roles.ldif file. Example 1 Examining Status of an EntryThe following command checks the status of Barbara Jensen's entry.
Example 2 Examining Status of a RoleThe following command checks the status of the Directory Administrators role.
AttributesSee attributes(5) for descriptions of the following attributes:
See Alsons-activate(1M), ns-inactivate(1M) NAME | Synopsis | Description | Options | Exit Status | Examples | Attributes | See Also ns-activate(1M)NAME | Synopsis | Description | Options | Exit Status | Examples | Attributes | See Also NAME
Synopsis
install-path/ds6/bin/ns-activate
[-D rootDN] {-w password | -w - | -j filename} [-p port]
[-h host] -I accountDN
DescriptionThe ns-activate command activates an account corresponding to an entry. The command can also be used to activate accounts sharing a role. Options
The following options are supported: Exit Status
The following exit values are returned: ExamplesThe examples in this section use sample data from the Example-roles.ldif file. Example 1 Activating an Inactive Account EntryThe following command activates Barbara Jensen's account.
Example 2 Activating an Inactive Account RoleThe following command activates the Directory Administrators role.
AttributesSee attributes(5) for descriptions of the following attributes:
See Alsons-accountstatus(1M), ns-inactivate(1M) NAME | Synopsis | Description | Options | Exit Status | Examples | Attributes | See Also ns-inactivate(1M)NAME | Synopsis | Description | Options | Exit Status | Examples | Attributes | See Also NAME
Synopsis
install-path/ds6/bin/ns-inactivate
[-D rootDN] {-w password | -w - | -j filename} [-p port]
[-h host] -I accountDN
DescriptionThe ns-inactivate command inactivates an account corresponding to an entry. The command can also be used to inactivate accounts sharing a role. Options
The following options are supported: Exit Status
The following exit values are returned: ExamplesThe examples in this section use sample data from the Example-roles.ldif file. Example 1 Inactivating an Account EntryThe following command inactivates Barbara Jensen's account.
Example 2 Inactivating an Account RoleThe following command inactivates the Directory Administrators role.
AttributesSee attributes(5) for descriptions of the following attributes:
See Alsons-accountstatus(1M), ns-activate(1M) NAME | Synopsis | Description | Options | Exit Status | Examples | Attributes | See Also replcheck(1M)NAME | Synopsis | Description | SUBCOMMANDS | GLOBAL OPTIONS | SUBCOMMAND OPTIONS | Operands | Extended Description | Exit Status | Attributes NAME
Synopsisinstall-path/ds6/support_tools/bin/replcheck subcommand options DescriptionThe replcheck command allows you to diagnose and repair a replication halt. Use the replcheck command with one of the options described in this man page. SUBCOMMANDS
The following subcommands are supported: GLOBAL OPTIONS
The following options are global, and are applicable to all commands and subcommands. SUBCOMMAND OPTIONS
The following options are applicable to the subcommands where they are specified. Operands
The following operands are supported: Extended Description
I The replcheck command diagnoses and repairs a replication halt. The replcheck diagnose subcommand compares the RUVs for each of the servers in your replication topology to determine if the masters are synchronized. If the search results show that all of the consumer replica in-memory RUVs are evolving on time or not evolving but equal to those on the supplier replicas, the tool will conclude that a replication halt is not occurring. However, if the command determines that the consumer RUVs do not change at all over time, then the replcheck diagnose subcommand displays the repair operation it would do and exits without making the repair. Then, you can launch the replcheck fix subcommand to repair the replication halt. For example, the command determines that replication is blocked on the entry associated with CSN 24 if a supplier has a CSN of 40, while the consumer has a CSN of 23 that does not evolve at all over time. The replcheck command can repair two types of replication halt: Exit StatusAttributesSee attributes(5) for descriptions of the following attributes:
NAME | Synopsis | Description | SUBCOMMANDS | GLOBAL OPTIONS | SUBCOMMAND OPTIONS | Operands | Extended Description | Exit Status | Attributes schema_push(1M)NAME | Synopsis | Description | Attributes | See Also NAME
Synopsisinstall-path/ds6/bin/schema_push instance-path DescriptionWhen schema modifications are made manually by editing the .ldif files such as 99user.ldif directly, the schema_push command should be run to update the modification time used by replication. This ensures that the modified schema are replicated to the consumers. The instance-path argument is the path to the instance where you updated schema files, such as /local/ds. Note – When using the command on Windows systems, you may need to include Perl in your PATH, as shown in the following example.
Once the script has been run, you must restart the server to trigger the schema replication. AttributesSee attributes(5) for descriptions of the following attributes:
See AlsoDS 6.2 Last Revised September 22, 2006NAME | Synopsis | Description | Attributes | See Also |
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|