Btw: How do you read this:
1522956ms th_a witness.cpp:240 block_production_loo ] slot: 1 scheduled_witness: 1.6.1537 scheduled_time: 2015-08-21T16:25:21 now: 2015-08-21T16:25:21
1523956ms th_a witness.cpp:240 block_production_loo ] slot: 2 scheduled_witness: 1.6.56 scheduled_time: 2015-08-21T16:25:22 now: 2015-08-21T16:25:22
1524185ms th_a application.cpp:348 handle_block ] Got block #76718 from network
1524234ms th_a application.cpp:443 get_item ] Request for item {"item_type":1001,"item_hash":"00012bae7445dfa925a756d82e6f68d9be6e20be"}
1524234ms th_a application.cpp:451 get_item ] Serving up block #76718
1524386ms th_a application.cpp:443 get_item ] Request for item {"item_type":1001,"item_hash":"00012bae7445dfa925a756d82e6f68d9be6e20be"}
1524386ms th_a application.cpp:451 get_item ] Serving up block #76718
Did Witness 1.6.1537 produce his block? Why is the init-witness directly "queueing up" or getting another slot then?