If I run fly m restart --select --signal SIGTERM the signal is ignored and a SIGINT is sent anyways. We have a kill_timeout in fly.toml of 5 minutes, so to restart an app it takes a long time without the custom signal. Am I doing something wrong?

I think I’ve fixed it for real this time, give it another shot

Fly CLI restart machine with custom signal not working

ben-io April 26, 2024, 9:55pm 4

Are you running the same command, fly m restart --select --signal SIGTERM? What is the output of fly logs when you run that?

`fly machine restart --signal <SIG>` fixed

Topic		Replies	Views
fly.toml kill_signal and kill_timeout Questions / Help	3	104	August 14, 2024
Fly.toml configuration does not set kill_signal machines , duplicated	12	45	November 7, 2024
`fly machine restart --signal <SIG>` fixed Fresh Produce machines	0	121	May 3, 2024
kill_timeout not working as expected JavaScript docs , nodejs , flyctl	5	668	August 30, 2023
fly deploy ignores --signal Questions / Help	1	15	September 21, 2024