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

#!/usr/bin/env ruby

# Connect to the listener, wait for the hello, then sigterm the
# listener.  We expect the listener to exit with a status of 6, which
# is enforced in the test.

require 'flexnbd/fake_source'
include FlexNBD

addr, port, pid = *ARGV

client = FakeSource.new(addr, port, 'Timed out connecting.')
client.read_hello

Process.kill('TERM', pid.to_i)

sleep(0.2)
client.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`

			`# Connect to the listener, wait for the hello, then sigterm the`
			`# listener. We expect the listener to exit with a status of 6, which`
			`# is enforced in the test.`

			`require 'flexnbd/fake_source'`
			`include FlexNBD`

			`addr, port, pid = *ARGV`

Rubocop 2018-02-02 21:34:14 +00:00			`client = FakeSource.new(addr, port, 'Timed out connecting.')`
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.read_hello`

Rubocop 2018-02-02 21:34:14 +00:00			`Process.kill('TERM', pid.to_i)`
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
			`sleep(0.2)`
			`client.close`

			`exit(0)`