diff options
| author | Ronnie Sahlberg <ronniesahlberg@gmail.com> | 2009-05-08 17:29:57 +1000 |
|---|---|---|
| committer | Ronnie Sahlberg <ronniesahlberg@gmail.com> | 2009-05-08 17:29:57 +1000 |
| commit | d6e1f04a670c4f0b96c2644471ccb4dc3fbd52c3 (patch) | |
| tree | 66e43017fbcf0ea8ab918a49056e174981d5efb3 /ctdb/packaging | |
| parent | e6e049060f4a0b165e13fa000f38ae673106fb7b (diff) | |
| download | samba-d6e1f04a670c4f0b96c2644471ccb4dc3fbd52c3.tar.gz samba-d6e1f04a670c4f0b96c2644471ccb4dc3fbd52c3.tar.xz samba-d6e1f04a670c4f0b96c2644471ccb4dc3fbd52c3.zip | |
new version 1.0.81
(This used to be ctdb commit a8019f20cd42a1965410fef5bac2c5b73657b38e)
Diffstat (limited to 'ctdb/packaging')
| -rw-r--r-- | ctdb/packaging/RPM/ctdb.spec | 14 |
1 files changed, 13 insertions, 1 deletions
diff --git a/ctdb/packaging/RPM/ctdb.spec b/ctdb/packaging/RPM/ctdb.spec index 12f7bdc959..ba8de4519b 100644 --- a/ctdb/packaging/RPM/ctdb.spec +++ b/ctdb/packaging/RPM/ctdb.spec @@ -4,7 +4,7 @@ Summary: Clustered TDB Vendor: Samba Team Packager: Samba Team <samba@samba.org> Name: ctdb -Version: 1.0.80 +Version: 1.0.81 Release: 1 Epoch: 0 License: GNU GPL version 3 @@ -132,6 +132,18 @@ fi %{_libdir}/pkgconfig/ctdb.pc %changelog +* Fri May 8 2009 : Version 1.0.81 + - use smbstatus -np instead of smbstatus -n in the 50.samba eventscript + since this avoids performing an expensive traverse on the locking and brlock + databases. + - make ctdb automatically terminate all traverse child processes clusterwide + associated to a client application that terminates before the traversal is + completed. + - From Sumit Bose : fixes to AC_INIT handling. + - From Michael Adam, add Tridge's "ping_pong" tool the the ctdb distro since + this is very useful for testing the backend filesystem. + - From Sumit bose, add support for additional 64 bit platforms. + - Add a link from the webpage to Michael Adams SambaXP paper on CTDB. * Fri May 1 2009 : Version 1.0.80 - change init shutdown level to 01 for ctdb so it stops before any of the other services - if we can not pull a database from a remote node during recovery, mark that node as a culprit so it becomes banned |