Bug#807456: #807456 to "A stop job is running" message should mention how to abort and what is making the message

[積丹尼 Dan Jacobson]

Actually it seems a "Failed to fork: Cannot allocate memory" triggered it.

Stopped LSB: No Display Manager.
Stopping ACPI event daemon...
Closed Load/Save RF Kill Switch Status /dev/rfkill Watch.
Deactivating swap /dev/sda12...
Stopped target Sound Card.
Stopping Session c1 of user jidanni.
Starting Store Sound Card State...
Stopping User Manager for UID 1000...
Stopped target Graphical Interface.
Stopped target Multi-User System.
Stopping Deferred execution scheduler...
Stopping D-Bus System Message Bus...
Stopped target Login Prompts.
acpid: exiting
Stopping Getty on tty1...
dictd.service: Failed to fork: Cannot allocate memory
Stopping LSB: Start and stop dictionary server daemon...
exim4.service: Failed to fork: Cannot allocate memory
Stopping LSB: exim Mail Transport Agent...
Stopping Regular background program processing daemon...
Stopping Self Monitoring and Reporting Technology (SMART) Daemon...
Stopping System Logging Service...
Stopped target Timers.
Stopped Daily Cleanup of Temporary Directories.
Stopped Regular background program processing daemon.
Stopped target Default.
Stopped target Basic System.
Stopped target Sockets.
Stopped target Paths.
Reached target Shutdown.
systemd-exit.service: Failed to fork: Cannot allocate memory
Assertion 'pid >= 1' failed at ../src/core/unit.c:2026, function unit_watch_pid(). Aborting.
rsyslogd: [origin software="rsyslogd" swVersion="8.14.0" x-pid="465" x-info="http://www.rsyslog.com"] exiting on signal 15.

But still, in the message you need to say who is making the message and
how to leave now.