keepalived
No description set
- Sources inherited from project Cloud:OpenStack:Rocky
- Download package
-
Checkout Package
osc -A https://api.opensuse.org checkout home:chajain/keepalived && cd $_
- Create Badge
Refresh
Refresh
Source Files
Filename | Size | Changed |
---|---|---|
keepalive-init.patch | 0000005805 5.67 KB | |
keepalive-rpmlintrc | 0000000115 115 Bytes | |
keepalived-1.4.5.tar.gz | 0000749813 732 KB | |
keepalived.changes | 0000028220 27.6 KB | |
keepalived.spec | 0000006413 6.26 KB |
Revision 2 (latest revision is 5)
Dirk Mueller (dirkmueller)
committed
(revision 2)
- update to 1.4.5: * Update snapcraft.yaml for 1.4.x+git * Fix generation of git-commit.h with git commit number. * Set virtual server address family correctly. * Set virtual server address family correctly when using tunnelled real servers. * Fix handling of virtual servers with no real servers at config time. * Add warning if virtual and real servers are different address families. Although normally the virtual server and real servers must have the same address family, if a real server is tunnelled, the address families can be different. However, the kernel didn't support that until 3.18, so add a check that the address families are the same if different address families are not supported by the kernel. * Send correct status in Dbus VrrpStatusChange notification. When an instance transitioned from BACKUP to FAULT, the Dbus status change message reported the old status (BACKUP) rather than the new status (FAULT). This commit attempts to resolved that. * doc: ipvs schedulers update * Fix a couple of typos in configure.ac. * Fix namespace collision with musl if_ether.h. * Check if return value from read_value_block() is null before using. * Fix reporting real server stats via SNMP. * Make checker process handle RTM_NEWLINK messages with -a option Even though the checker process doesn't subscribe to RTNLGRP_LINK messages, it appears that older kernels (certainly 2.6.32) can send RTM_NEWLINK (but not RTM_DELLINK) messages. This occurs when the link is set to up state. Only the VRRP process is interested in link messages, and so the checker process doesn't do the necessary initialisation to be able to handle RTM_NEWLINK messages.
Comments 0