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.
I understand the idea behind this: the operating system sends SIGTERM, I suppose, to the program, and it doesn't terminate.
I suppose that sending SIGKILL is safer, less of a chance that data is lost for a program that manages to clean up after itself and stop gracefully.
- You can change some timeouts, shutdown in a different way.
- There isn't a key combination you can punch in, if you as a user want to override this, like 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. Why is there no way to just stop this
A stop job is running for Session c2 of user waiting for timeout message?