@lattera @jimsalter It wouldn't even make sense to trap SIGINFO and exit or crash; if you're writing a tool primarily aimed at Linux you likely never even know SIGINFO exists and if the software doesn't recognize SIGINFO nothing should happen or any stray signal would cause the same problem.

I *do* have a memory of some brain-damaged Linux tool that did crazy things with signals... *scratching head*... GNU dd requires you send SIGUSR1 to get statistics but that's not it. There's another piece of software I've run into in the last 10 years that did something absolutely crazy when it received a SIGHUP. I think it treated it like SIGTERM.

I'd be willing to bet money this never happened and it was something else misbehaving with SIGHUP.