|
|
squid: Allow access to only one site and only via 80 or 443
|
|
vxsited(1M) vxsited(1M) NAME
vxsited - site monitoring daemon SYNOPSIS
/etc/vx/bin/vxsited [mail_address...] DESCRIPTION
The vxsited daemon monitors Veritas Volume Manager (VxVM) for disks being attached, and reattaches a detached site if the disks that belong to that site become accessible. vxsited analyzes the output of the vxnotify command, and waits for a failed disk to attach. When a disk is attached, vxsited attempts to online the disk, and tries to reattach the failed site. If a site is successfully reattached, vxsited starts recovery using vxrecover, and sends mail to root (by default) or to other specified users. Mail Notification By default, vxsited sends mail to root with information about the disk status of any attempts to reattach the site. To send mail to other users, add the user login name to the line that starts vxsited in the startup script, /etc/init.d/vxvm-recover, and reboot the system. For example, if the line appears as: nohup vxsited root & and you want mail also to be sent to user1 and user2, change the line to read: nohup vxsited root user1 user2 & Alternatively, kill the vxsite process, and restart it from the command line with the required mail addresses as arguments. The mail notification has a format that is similar to the following: Subject : Volume Manager site reattach on host hostname Reattached site sitename in disk-group diskgroup Reattachment Procedure If a disk from a detached site becomes accessible again, vxsited checks whether the relocation daemon, vxrelocd, is running. If vxrelocd is running, vxsited attempts to reattach the site. The relocation daemon can then try to relocate the failed subdisks using space on the available disks in the disk group. If the failed objects are successfully relocated, vxrelocd changes the state of the site to RECOVER, and starts the recovery of volumes at the site. When all the plexes at a site have been recovered, the plexes are put into the ACTIVE state, and the state of the site is set to ACTIVE. If vxrelocd is not running, vxsited only reattaches a site when all the disks from that site become accessible. After successfully reat- taching a site, vxsited changes the site state to ACTIVE, and initiates recovery using vxrecover. When all the plexes from a site have been recovered, the plexes are put into the ACTIVE state, and the state of the site is set to ACTIVE. vxsited does not attempt to reattach a site that has been explicitly detached by an administrator. The state OFFLINE is set for sites that have been detached by using the following command: vxdg -g dg_name detachsite sitename Disabling vxsited If you do not want a site to be recovered automatically, kill the vxsited daemon, and prevent it from restarting. To kill the daemon, run the following command from the command line, and locate the process table entry for vxsited: ps -ef Execute the command: kill -9 PID Substitute the process ID of the vxsited process for PID. To prevent vxsited from being restarted, comment out the line that starts vxsited in the startup script /sbin/init.d/vxvm-recover. FILES
/sbin/init.d/vxvm-recover The startup file for vxsited. SEE ALSO
kill(1), mailx(1), ps(1), vxdg(1M), vxrelocd(1M), vxintro(1M), vxnotify(1M), vxrecover(1M) VxVM 5.0.31.1 24 Mar 2008 vxsited(1M)
