| United States-English |
|
|
|
![]() |
VERITAS Volume Manager 3.5 Administrator's Guide > Chapter 9 Administering
Hot-RelocationModifying the Behavior of Hot-Relocation |
|
Hot-relocation is turned on as long as vxrelocd is running. You leave hot-relocation turned on so that you can take advantage of this feature if a failure occurs. However, if you choose to disable this feature (perhaps because you do not want the free space on some of your disks to be used for relocation), prevent vxrelocd from starting at system startup time. You can stop hot-relocation at any time by killing the vxrelocd process (this should not be done while a hot-relocation attempt is in progress). You can make some minor changes to the way vxrelocd behaves by either editing the vxrelocd line in the startup file that invokes vxrelocd (/sbin/rc2.d/S95vxvm-recover), or by killing the existing vxrelocd process and restarting it with different options. After making changes to the way vxrelocd is invoked in the startup file, you need to reboot the system so that the changes go into effect. If you choose to kill and restart the daemon instead, make sure that hot-relocation is not in progress when you kill the vxrelocd process. You should also restart the daemon immediately so that hot-relocation can take effect if a failure occurs. You can alter vxrelocd behavior as follows:
When executing vxrelocd manually, either include /etc/vx/bin in your PATH or specify vxrelocd's absolute pathname, for example:
or # nohup /etc/vx/bin/vxrelocd root user1 user2 & See the vxrelocd(1M) manual page for more information. |
|||||||||||||||||||||||||||||||||||||||||||||||||
|
|||||||||||||||