Alex Young f3e0d61323 Quit with an error status on SIGTERM during migration ...

This prevents the supervisor from thinking that the migration completed
successfully.

In order to do this, I've introduced a new lock around the start (and
finish) of the migration so that we avoid a race between the signal
handler in the server_accept loop and the control thread mirror startup.
Without that, we'd risk successfully starting a migration after the
SIGTERM handler fired, which would be Bad.

2012-10-04 14:41:55 +01:00

..

break_after_hello.rb

Remove listen mode

2012-07-23 09:48:50 +01:00

close_after_entrust_reply.rb

Handle a failed disconnect correctly

2012-07-12 09:39:39 +01:00

close_after_hello.rb

Test that a disconnect after the write request but before the data is an error

2012-07-03 15:25:39 +01:00

close_after_write.rb

Test that a disconnect after the write request but before the data is an error

2012-07-03 15:25:39 +01:00

close_after_writes.rb

Simplify the migration handover protocol

2012-07-23 10:22:25 +01:00

error_on_write.rb

Test that a disconnect after the write request but before the data is an error

2012-07-03 15:25:39 +01:00

hang_after_connect.rb

Move the mirror commit state mbox to struct control

2012-07-15 21:57:36 +01:00

hang_after_write.rb

Test that a disconnect after the write request but before the data is an error

2012-07-03 15:25:39 +01:00

hello_wrong_magic.rb

Switch from expecting a reconnection to *not* doing do

2012-07-15 22:07:00 +01:00

hello_wrong_size.rb

Don't retry a mirror which failed on the first attempt

2012-07-15 20:07:17 +01:00

reject_acl.rb

Switch from expecting a reconnection to *not* doing do

2012-07-15 22:07:00 +01:00

sigterm_after_hello.rb

Quit with an error status on SIGTERM during migration

2012-10-04 14:41:55 +01:00

write_wrong_magic.rb

Test that a write reply with the wrong magic will force a retry

2012-07-03 17:01:39 +01:00