Mail Archive Search: <+subject:/^(?:^\s*(re|sv|fwd|fw)[\[\]\d]*[:>-]+\s*)*\[lvs\-users\]\s+keepalive\s+config\s+files\s+to\s+monitor\s+all\s+ports\s*$/>

Results:

References: [ +subject:/^(?:^\s*(re|sv|fwd|fw)[\[\]\d]*[:>-]+\s*)*\[lvs\-users\]\s+keepalive\s+config\s+files\s+to\s+monitor\s+all\s+ports\s*$/: 2 ]

Total 2 documents matching your query.

1. Re: [lvs-users] keepalive config files to monitor all ports (score: 1): Author: Khosrow Ebrahimpour <khosrow.ebrahimpour@xxxxxxxxxxxxx>; Date: Wed, 19 Mar 2014 11:38:43 -0400; Assuming you only want to check a few ports, you could use the MISC_CHECK option in keepalived. This allows you to write your own check script, where you could loop through all the ports that you car; /html/lvs-users/2014-03/msg00049.html (10,178 bytes)
2. [lvs-users] keepalive config files to monitor all ports (score: 1): Author: yang feng <hoking.yang@xxxxxxxxx>; Date: Mon, 10 Mar 2014 19:39:19 +0800; I want to set up a keepalive + LVS system. I can use /sbin/ipvsadm -A -t $VIP:0 -s wrr -p 60 /sbin/ipvsadm -a -t $VIP:0 -r $RIP1:0 -g to foward all connections from VIP to realserver. But if I use ke; /html/lvs-users/2014-03/msg00037.html (8,982 bytes)

Current List: 1 - 2
Page: [1]