flexnbd-c/tests/acceptance/fakes/dest/sigterm_after_hello.rb

#!/usr/bin/env ruby

# Wait for a sender connection, send a correct hello, then sigterm the
# sender.  We expect the sender to exit with status of 6, which is
# enforced in the test.

require 'flexnbd/fake_dest'
include FlexNBD

addr, port, pid = *ARGV
server = FakeDest.new(addr, port)
client = server.accept('Timed out waiting for a connection')
client.write_hello

Process.kill(15, pid.to_i)

client.close
server.close
exit 0
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			`#!/usr/bin/env ruby`

			`# Wait for a sender connection, send a correct hello, then sigterm the`
			`# sender. We expect the sender to exit with status of 6, which is`
			`# enforced in the test.`

			`require 'flexnbd/fake_dest'`
			`include FlexNBD`

			`addr, port, pid = *ARGV`
Rubocop 2018-02-02 21:34:14 +00:00			`server = FakeDest.new(addr, port)`
			`client = server.accept('Timed out waiting for a connection')`
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			`client.write_hello`

			`Process.kill(15, pid.to_i)`

			`client.close`
			`server.close`
			`exit 0`