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

[Ronnie Sahlberg]

The annotated tag, ctdb-1.0.91 has been created
        at  3ea59c1a057805c9053b73f53d1ad90102606b28 (tag)
   tagging  d1332f4d5d3d3e4b4e0cd362a6903d09e0d5fcbb (commit)
  replaces  ctdb-1.0.90
 tagged by  Ronnie Sahlberg
        on  Tue Sep 29 13:34:56 2009 +1000

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

iD8DBQBKwYBu2aJ36aon/y8RAqzVAJwI1POVfcEBhq3ZOJb9uT6Z3CwrWACfSyRe
p68IW33ALMz+uMaKDiSskaE=
=/lK/
-----END PGP SIGNATURE-----

Martin Schwenke (3):
      Test suite: Rework the cluster (re)start code.
      Test suite: wait_until_node_has_status() now uses "onnode any".
      Test suite: Update "complex" tests for wait_until_node_has_status() change.

Mathieu Parent (5):
      Fix bashism in natgw eventscript.
      Fix bashisms in multipathd event script.
      Fix bashisms in samba event script.
      Fix bashism in nfstickle event script.
      Update outdated autotools helper files.

Michael Adam (6):
      Rename the CTDB_INIT_STYLE "ubuntu" to "debian" - this is where it comes from.
      ctdb_logging: fix a comment typo.
      Introduce sysconfig variable CTDB_SYSLOG=yes/no (default "no").
      ctdb_client: fix race in starting concurrent transactions on a single node
      Revert "allow the transaction commit to fail"
      Revert "dont check if commit failed, we do allow the commit to fail sometimes"

Ronnie Sahlberg (14):
      Merge commit 'obnox/master-rebase'
      try to restart statd everytime it fails, not just the first time
      Revert "try to restart statd everytime it fails, not just the first time"
      try restarting ststd indefinitely   not just once
      dont mark the recovery daemon as a ban culprit just because a node in the cluster was set to recvoery mode == ACTIVE.
      Merge commit 'martins/master'
      with the new banning logic with one struct for each node we no longer "forget" the other culprits as often as we used to do, which means that things like "ctdb recover" can now actually lead to a node becomming banned if we perform too many recoveries too frequently.
      Merge root at 10.1.1.27:/shared/ctdb/ctdb-git
      Merge commit 'obnox/master-rebase'
      add machinereadable output for the ctdb getreclock command
      add a new eventscript 01.reclock
      change the reclock fail count to 19 monitor intervals before we shut down ctdbd
      From Wolfgang Mueller-Friedt
      New version 1.0.91

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


-- 
CTDB repository