Keepalived for Linux 1.1.17 (Default branch)


 
Thread Tools Search this Thread
Special Forums News, Links, Events and Announcements Software Releases - RSS News Keepalived for Linux 1.1.17 (Default branch)
# 1  
Old 03-05-2009
Keepalived for Linux 1.1.17 (Default branch)

Keepalived for LVS aims to add a strong and robust keepalive facility to the Linux Virtual Server project. This project is written in C with multilayer TCP/IP stack checks. It implements a framework based on three family checks: Layer3, Layer4, and Layer5. This framework gives the daemon the ability of checking a LVS server pool states.When one of the servers in the LVS server pool is down, keepalived informs the Linux kernel via a setsockopt call to remove this server entry from the LVS topology. In addition, it implements a VRRPv2 stack to handle director failover. License: GNU General Public License (GPL)Changes:
A regression brought by the previous release during low-level scheduler timer computation was fixed. VRRP MII code was fixed to properly test BMSR. VRRP script initialization was optimized.Image

Image

More...
Login or Register to Ask a Question

Previous Thread | Next Thread

2 More Discussions You Might Find Interesting

1. Linux

The problem in the Haproxy+Keepalived script

Hi Install HAPROXY+KEEPALIVED in the hosts ip 192.168.10.241 & 192.168.20.241 And was configured as follows: KeepAlived vrrp_script chk_haproxy { script "pidof haporxy" # check the haproxy process interval 2 # every 2 seconds weight 2 # add 2 points if OK } vrrp_instance VI_1 {... (1 Reply)
Discussion started by: milad
1 Replies

2. UNIX for Dummies Questions & Answers

Keepalived and Source Hash Scheduling

Hello guys, Hope you are doing great!! Right now I'm using keepalived daemon in order to ensure a Load Balancing function between my two servers. First of all, I tried using the famous "Round-Robin Scheduling" algorithm and it worked well, but I'm kind of obligated to use the "Source Hashing ... (7 Replies)
Discussion started by: biks93
7 Replies
Login or Register to Ask a Question
GET_ROBUST_LIST(2)						Linux System Calls						GET_ROBUST_LIST(2)

NAME
get_robust_list, set_robust_list - get/set list of robust futexes SYNOPSIS
#include <linux/futex.h> #include <syscall.h> long get_robust_list(int pid, struct robust_list_head **head_ptr, size_t *len_ptr); long set_robust_list(struct robust_list_head *head, size_t len); Note: There are no glibc wrappers for these system calls; see NOTES. DESCRIPTION
The robust futex implementation needs to maintain per-thread lists of robust futexes which are unlocked when the thread exits. These lists are managed in user space; the kernel is only notified about the location of the head of the list. The get_robust_list() system call returns the head of the robust futex list of the thread whose thread ID is specified in pid. If pid is 0, the head of the list for the calling thread is returned. The list head is stored in the location pointed to by head_ptr. The size of the object pointed to by **head_ptr is stored in len_ptr. The set_robust_list() system call requests the kernel to record the head of the list of robust futexes owned by the calling thread. The head argument is the list head to record. The len argument should be sizeof(*head). RETURN VALUE
The set_robust_list() and get_robust_list() system calls return zero when the operation is successful, an error code otherwise. ERRORS
The set_robust_list() system call can fail with the following error: EINVAL len does not match the size of structure struct robust_list_head expected by kernel. The get_robust_list() system call can fail with the following errors: EPERM The calling process does not have permission to see the robust futex list of the thread with the thread ID pid, and does not have the CAP_SYS_PTRACE capability. ESRCH No thread with the thread ID pid could be found. EFAULT The head of the robust futex list can't be stored at the location head. VERSIONS
These system calls were added in Linux 2.6.17. No library support is provided; use syscall(2). NOTES
These system calls are not needed by normal applications. No support for them is provided in glibc. In the unlikely event that you want to call them directly, use syscall(2). A thread can have only one robust futex list; therefore applications that wish to use this functionality should use the robust mutexes pro- vided by glibc. SEE ALSO
futex(2) Documentation/robust-futexes.txt and Documentation/robust-futex-ABI.txt in the Linux kernel source tree COLOPHON
This page is part of release 3.44 of the Linux man-pages project. A description of the project, and information about reporting bugs, can be found at http://www.kernel.org/doc/man-pages/. Linux 2012-07-13 GET_ROBUST_LIST(2)