In a typical modern Linux distribution, the user may experience this when trying to shut down the computer:
"A stop job is running for Session c2 of user", or equivalent.
Now, I understand the idea behind this: The OS sends SIGTERM, I suppose, to the program, and it doesn't terminate. Why send it SIGKILL, when you can wait and see if the program manages to clean up after itself and stop gracefully? This is safer, less of a chance that data is lost, and work is lost.
However, why is there NO WAY to just stop this?
Yeah, sure, you can change some timeouts, shutdown in a different way, maybe there are some other tricks.
My question is: Why isn't there a simple key combination you can punch in, if you as a user want to override this? Why can't I simply do control + D, or control + C to cancel it and just send SIGKILL immediately?
I hope there is some logical reasoning behind this design choice, because to me, it seems awfully similar to how e.g. Windows deals with a process that isn't "responding" and seems very inspired from that.