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

[Ronnie Sahlberg]

The annotated tag, ctdb-1.0.100 has been created
        at  4c3be998d3c752dad309c6fab0f9d868148a3983 (tag)
   tagging  fa34e8a5d588026029dca949151697817fe7f127 (commit)
  replaces  1.0.99
 tagged by  Ronnie Sahlberg
        on  Wed Oct 28 16:12:15 2009 +1100

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

iD8DBQBK59LA2aJ36aon/y8RAoKzAKCM4N4aTK7yZb7jBV6xrjKjmytQjwCghyhs
edJssuNGTvlOXNi8X+8FeRM=
=UEdB
-----END PGP SIGNATURE-----

Martin Schwenke (15):
      initscript: when stopping on Red Hat use the success/failure functions.
      Merge commit 'origin/master'
      Merge branch 'onnode_options'
      Merge commit 'origin/master'
      Test suite: add -x option to ctdb_init() function.
      Test suite: Fix bug in node_has_status().
      Test suite: Update 99_ctdb_uninstall_eventscript.sh to use ctdb_init().
      Test suite: New tests for validating SKIP_SHARE_CHECK options.
      Merge commit 'origin/master'
      Test suite: A timeout of MonitorInterval seconds sometimes isn't enough.
      Test suite: Fix the timeouts on the skip share check tests.
      Test suite: Remove the disable/enable monitor tests - they are useless.
      Merge commit 'origin/master'
      Document onnode -n and -f options.
      Merge commit 'origin/master'

Ronnie Sahlberg (17):
      Merge commit 'martins/master'
      set the eventscripts to timeout after 20 seconds
      when scripts timeout, log pstree to a file in /tmp and just log the filename in the messages file
      Add a mechanism where we can register notifications to be sent out to a SRVID when the client disconnects.
      lower the log level of a debug message
      automatically re-activate the reclock file check if we set the reclock file to something
      update the manpage for ctdb setreclock
      disabel the multipath eventscript by default
      Suggestion from Volker,
      patch the event loop so we read the current time every iteration.
      for debugging
      dont run the monitor event so frequently after a event has failed.
      temporarily try allowing clients to attach to databases even if the node is banned/stopped or inactive in any other way.
      add a check that winbind can actually talk to teh dc during the startup event
      Enhance the logging fromeventscripts.
      change the eventscript handling to allow EventScriptTimeout for each individual script isntead of for the entire set of scripts
      new version   1.0.100

Stefan Metzmacher (5):
      tcp: don't log an error when we succefully bind to the desired address
      server: print out the full 64-bit srvid on 32-bit hosts
      server: if takeover runs when the recovery master becomes unhealthy
      ctdb_client: fix DEBUG statement in ctdb_ctrl_modflags()
      ctdb_diagnostics: don't use hardcoded path to iptables

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


-- 
CTDB repository