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

[Ronnie Sahlberg]

The annotated tag, ctdb-1.0.102 has been created
        at  6e585176578d135375f788e7598b40b28abd30e9 (tag)
   tagging  4892222ffb255dccd8ced1cb047f199386bb3e98 (commit)
  replaces  ctdb-1.0.101
 tagged by  Ronnie Sahlberg
        on  Thu Oct 29 13:43:21 2009 +1100

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

iD8DBQBK6QFW2aJ36aon/y8RAqPDAKCALDmn5K9vY5yx0I36mvr0dZ5IpACfbw60
kQ7HPuc2MAIUxFLGYy4ARc8=
=JIH0
-----END PGP SIGNATURE-----

Michael Adam (4):
      server: add a new ctdb control CTDB_TRANS2_ACTIVE
      client: add ctdb_ctrl_transaction_active() which calls out to CTDB_TRANS2_ACTIVE
      client: fix race condition with concurrent transactions on the same node.
      ctdb_client: reformat a comment slightly to enhance clearness.

Ronnie Sahlberg (7):
      update the "uptime" command to indicate the "time since last" is the time since the last recovery OR failover.
      update the manpage for "update" to indicate the "time since last" indicates
      Revert "update the "uptime" command to indicate the "time since last" is the time since the last recovery OR failover."
      update the uptime command to indicate that time since last is either from alst recovery or from last failover
      make the error logged when winbindd fails to access the dc during startup more scary and easier to spot in the logs
      Revert "From Wolfgang M."
      new version 1.0.102

Wolfgang Mueller-Friedt (2):
      vacuuming needed additional check before getting rid of the record; there is a gap between selecting the records and deleting them, therefore we have to check if the records still can be deleted when we actually are about to delete them
      ensure tdb names end with .tdb. and any number of digits

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


-- 
CTDB repository