Volume Manager Daemons

Startup scripts invoke the vxconfigd daemon during the boot procedure.

To determine whether the volume daemon is enabled, use the following command:

	# vxdctl mode

This message is displayed if the vxconfigd daemon is running and enabled:

	mode: enabled

This message is displayed if vxconfigd is running, but not enabled:

	mode: disabled

To enable the volume daemon, use the following command:

	# vxdctl enable

This message is displayed if the vxconfigd daemon is not running:

mode: not-running

To start the vxconfigd daemon, use the following command:

	# vxconfigd

Once started, the vxconfigd daemon automatically becomes a background process.

By default, the vxconfigd daemon issues errors to the console. However, the vxconfigd daemon can be configured to issue errors to a log file.

For more information, see the vxconfigd(1M) and vxdctl(1M) manual pages.

The vxiod daemons are started at system boot time. There are typically several vxiod daemons running at all times. Rebooting after your initial installation starts the vxiod daemon.

Verify that vxiod daemons are running by entering this command:

	# vxiod

Because the vxiod daemon is a kernel thread and is not visible to you through the ps command, this is the only way to see if any vxiod daemons are running.

If any vxiod daemons are running, the following message is displayed:

	10 volume I/O daemons running

where 10 is the number of vxiod daemons currently running.

If no vxiod daemons are currently running, start some by entering this command:

	# vxiod set 10

where 10 can be substituted by the desired number of vxiod daemons. It is recommended that at least one vxiod daemon exist for each CPU in the system.