Query: voliod
OS: osf1
Section: 8
Format: Original Unix Latex Style Formatted with HTML and a Horizontal Scroll Bar
voliod(8) System Manager's Manual voliod(8)NAMEvoliod - Start, stop, and report on Logical Storage Manager kernel daemonsSYNOPSIS/sbin/voliod /sbin/voliod [-f] set countOPTIONSThe following option is used by voliod: Force the kill of the last I/O daemon. Without this option, the I/O daemons can only be reduced to one.DESCRIPTIONThe voliod utility starts, stops, or reports on Logical Storage Manager I/O daemons. An I/O daemon is a process that provides a process context for processing any work that needs to be done to process Logical Storage Manager I/O. When invoked with no arguments, voliod prints the current number of volume I/O daemons on the standard output. When invoked with the set keyword, the number of daemons specified by count will be created. If more volume I/O daemons exist than are specified by count, then the excess processes will be terminated. If more than the maximum number are created (currently 64), the requested number will be silently truncated to that maximum. The number of daemons to create for general I/O handling depends on system load and usage. One daemon for each CPU on the system is gener- ally adequate, unless volume recovery seems unusually slow. Each I/O daemon starts in the background and creates an asynchronously-running kernel thread and becomes a volume I/O daemon. The voliod utility does not wait for these threads to complete.NOTESLSM automatically sets the number of I/O daemons when the system starts, so it is usually not necessary to set or change the number of I/O daemons with this command. LSM I/O daemons cannot be killed directly through the use of signals. The number of Logical Storage Manager I/O daemons currently running can only be determined by running voliod; I/O daemons do not appear in the list of processes produced by the ps(1) command.EXIT CODESThe voliod utility prints a diagnostic on the standard error, and exits if an error is encountered. If an I/O error occurs within a spawned I/O daemon thread, then the I/O is not reflected in the exit status for voliod. Otherwise, voliod returns a nonzero exit status on errors. Usage errors result in an exit status of 1 and a usage message. If the requested number of daemons cannot be created, then the exit status is 2, and the number of daemons that were successfully started is reported. If any other error occurs, the exit status is 3.FILESThe device used to report on and start volume I/O daemon kernel threads.SEE ALSOfork(2), volintro(8), vold(8), voldctl(8) ,pthread(8) voliod(8)
Related Man Pages |
---|
voliod(8) - osf1 |
utxd(8) - osf1 |
voldctl(8) - osf1 |
volsetup(8) - osf1 |
rpc.lockd(8) - osf1 |
Similar Topics in the Unix Linux Community |
---|
Taming your daemons with PSMon |
bash logging al $() command lines |
Command to list down all daemons in Solaris |
Daemon monitoring |
Kill multiple processes ran by root |