Due to to people kill-9'ing rpm when it waits with signals blocked ( see for example bug #73097 ), I suggest using a signal handler that prints a notice and continues, so people would not use kill -9 right away. Something like "rpm is currently busy doing this-and-this, please wait a monent" or whatever is more informative.
Nobody wants to know when signals are blocked. What is desired is functionality, not ever more obscure and arcane messages.
I think you misunderstood me. The message should not be printed alwys, but only if a blocked signal is received. Example, current behavior : - rpm is running, signals are blocked, no appareng disc activity - user : "hmm, weird, I'll stop it." - user press ctrl-c - user : "Uh, nothing happened. It is hung. I'll kill -9 it." Example, proposed behavior : - rpm is running, signals are blocked, no appareng disc activity - user : "hmm, weird, I'll stop it." - user press ctrl-c - rpm : "Hey! I'm busy doing stuff" - user : "Oh, in that case I'll wait a bit longer"
The signal handlers are localed in rpmlib which is used in graphical contexts where there is no guarantee that output is possible, let alone desireable.