The annotated tag, ctdb-1.0.83 has been created
at f895cb575e80a1458981e24af2594e962b41c0ef (tag)
tagging f236fa289f3115b1f4eb108eb668392dc520f61a (commit)
replaces ctdb-1.0.82
tagged by Ronnie Sahlberg
on Tue Jun 2 13:00:50 2009 +1000
- Log -----------------------------------------------------------------
tag for 1.0.83
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)
iD8DBQBKJJXv2aJ36aon/y8RApF7AKCDqYjnyEp/rq4siw2qcgr8AOLvbQCfbPPq
fThTneAjKvZdOyx+jhLac0E=
=VDFn
-----END PGP SIGNATURE-----
Christian Ambach (1):
Remove error messages about a non-existing /var/log/log.ctdb when running
ctdb with logging to syslog
Ronnie Sahlberg (26):
Track how long it takes to take out the recovery lock from both the main
dameon and also from the recovery daemon.
add additional log info to track if/why we cant switch to client mode.
From : Flavio Carmo Junior <[email protected]>
Change the loglevel of "registered tcp client for ..." to INFO
Whitespace changes and using the CTDB_NO_MEMORY() macro changes to
change the socket we use for sending grautious ARPs from
AF_INET/SOCK_PACKET to AF_PACKET/SOCK_RAW
document the new support for ClamAV
From Flavio Carmo Junior <[email protected]>
From Flavio Carmo Junior <[email protected]>
add 31.clamd to the install and the rpm
install the 31.clamd script as 644 by default
fix the git path to the repository
remove the obsolete ipmux component.
Revert "add TDB_NO_NESTING. When this flag is set tdb will not allow any
nested transactions and tdb_transaction_start() will implicitely _cancel() any
pending transactions before starting any new ones."
Revert "set the TDB_NO_NESTING flag for the tdb before we start a
transaction from within recovery"
Revert "we only need to have transaction nesting disabled when we start
the new transaction for the recovery"
New attempt at TDB transaction nesting allow/disallow.
dont remove the socket when the dameon stops. This can race if the
add a new node state : DELETED.
use num_nodes and the nodes array instead of walking the vnnmap
when building the initial vnnmap, make sure to skip any deleted nodes
dont try to queue packets for sending to (recently) deleted nodes since
these nodes do not have a queue.
lower the loglevel when we long that we skip an evenscript because it is
not executable
hide all DELETED nodes from the ctdb command output
idocument how to remove a node from an existing cluster using 'ctdb
new version 1.0.83
Sumit Bose (6):
added a missing dependency
fix a configure warning while checking for netfilter.h
structure member logfile is not used anywhere
structure member node_list_file is not used anywhere
add missing checks on so far ignored return values
fix re pattern to accept the new recovery lock times in the statistics
output
Volker Lendecke (1):
Fix http://ctdb.samba.org/download.html
-----------------------------------------------------------------------
--
CTDB repository
