[SCM] CTDB repository - annotated tag ctdb-1.0.95 created - ctdb-1.0.95

[Ronnie Sahlberg]

The annotated tag, ctdb-1.0.95 has been created
        at  30ca928b3cc057ede4746956e8541bd0d24c6282 (tag)
   tagging  3501d6b70bd905d6fdc4e74fe2cedc3ba77e4b86 (commit)
  replaces  ctdb-1.0.93
 tagged by  Ronnie Sahlberg
        on  Mon Oct 12 18:53:52 2009 +1100

- Log -----------------------------------------------------------------
tag for 1.0.95
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)

iD8DBQBK0uCf2aJ36aon/y8RAlOsAJ0SDGSN+/9OpwFICN6gEFlhpPWyfQCeMd6G
WwyjsKR/sGoFtS1eCP8xzZI=
=oYXi
-----END PGP SIGNATURE-----

Martin Schwenke (2):
      40.vsftpd: reset the fail counter in the "recovered" event.
      Clean up ctdb_check_directories* eventscript functions.

Ronnie Sahlberg (15):
      if a node fails to become frozen during recovery, mark it up with as a culprit so it will soon get banned
      version 1.0.94
      Fix bug spotted by Metze,
      verify the DISABLED flag and compare with the previous flag we have registered for that node and not what the node says is the difference.
      add a control to set a database priority. Let newly created databases default to priority 1.
      add a control to read the db priority from a database
      during recovery, update all remote nodes so they use the same priorities
      uptade the freeze/thaw commands to be able to send the requested database priority to freeze/thaw to the daemon.
      initial attempt at freezing databases in priority order
      allow setting the recmode even when not completely frozen.
      add a new control for explicitely cancelling recovery transactions, i.e. the
      Merge commit 'martins/master'
      add a dispatch to the recovery transaction cancel call
      use the correct expected size for thew _cancel control
      new version 1.0.95

-----------------------------------------------------------------------


-- 
CTDB repository