Fix for bug#23169 - memset param switching

into  willster.(none):/home/stewart/Documents/MySQL/5.1/ndb

into  perch.ndb.mysql.com:/home/jonas/src/mysql-5.1-new-ndb

into  perch.ndb.mysql.com:/home/jonas/src/51-work

  note this does not happen in 5.0, but i'm committing it here to keep code same between 5.0 and 5.1

into  perch.ndb.mysql.com:/home/jonas/src/51-work

into  perch.ndb.mysql.com:/home/jonas/src/50-work

  Fix race-condition between COPY_GCIREQ (GCP) and lcpSetActiveStatusEnd
  Solution is _not_ to copy sysfileData from COPY_GCIREQ from "self"

into  neptunus.(none):/home/msvensson/mysql/mysql-5.1

into  neptunus.(none):/home/msvensson/mysql/mysql-5.1

into  neptunus.(none):/home/msvensson/mysql/mysql-5.0

into  neptunus.(none):/home/msvensson/mysql/mysql-5.1

into  orca.ndb.mysql.com:/export/home/space/pekka/ndb/version/my51-ndb

into  mysql.com:/home/bk/MERGE/mysql-5.1-merge

into  mysql.com:/home/bk/MERGE/mysql-5.0-merge

into  perch.ndb.mysql.com:/home/jonas/src/mysql-5.1-new-ndb

  ndb_restore Return OK even if temporary errors
    (otherwise mysql-test-run/ndb_restore can fail on really slow machines)

into  romeo.(none):/home/bk/b21474-mysql-5.1-new-rpl

Removing code to step the group log position and just stepping
the event log position.  If the group log position were stepped
one time too many, it might be that the group starts at a position
that is not possible, e.g., at a Rows_log_event, or between an
Intvar_log_event and the following associated Query_log_event.

into  trift2.:/MySQL/M50/push-5.0

Replacing C++ code with C code in a C file.

into  perch.ndb.mysql.com:/home/jonas/src/mysql-5.1-new-ndb

into  perch.ndb.mysql.com:/home/jonas/src/mysql-5.1-new-ndb

into  perch.ndb.mysql.com:/home/jonas/src/51-work

  fix bug in test prg

  fix bug in handling of inactive timeout for scan, when all is delivered

into  orca.ndb.mysql.com:/export/home/space/pekka/ndb/version/my51-bug20446

into  orca.ndb.mysql.com:/export/home/space/pekka/ndb/version/my51-bug20446

into  mysql.com:/home/svoj/devel/mysql/engines/mysql-5.0-engines

into  mysql.com:/home/svoj/devel/mysql/engines/mysql-5.1-engines

into  may.pils.ru:/home/svoj/devel/bk/mysql-5.1-engines

into  may.pils.ru:/home/svoj/devel/bk/mysql-5.0-engines

  Add checking of REDO to earlier during SR
      so take-over of node can be performed
      if it can't be restarted using logs
      (which btw is really weird...as it _should_ be able to use logs of other node in node group)

  Otherwise cluster could be started and 1 fragment on one node could not have been restored
  Making the cluster inconsisten, VERY BAD