VERITAS Volume Manager 3.1 Administrator's Guide

Initialization and Setup
Volume Manager Daemons
Chapter 272
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.
Volume I/O Daemon vxiod
The volume extended I/O daemon (vxiod) allows for extended I/O
operations without blocking calling processes.
For more information, see the vxiod (1M) manual page.
Starting the Volume I/O Daemon
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.