Bug 716609 - Cannot stop, start, restart or reload a service if "Scroll Lock" key ist pressed in the console tty
Summary: Cannot stop, start, restart or reload a service if "Scroll Lock" key ist pres...
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Fedora
Classification: Fedora
Component: systemd
Version: 15
Hardware: i686
OS: Linux
unspecified
high
Target Milestone: ---
Assignee: Lennart Poettering
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-06-25 12:57 UTC by Michael Weidner
Modified: 2011-08-31 00:49 UTC (History)
7 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2011-08-31 00:49:16 UTC
Type: ---


Attachments (Terms of Use)

Description Michael Weidner 2011-06-25 12:57:57 UTC
I am running Fedora 15 on a small server without grafical user interface (boots in text mode).

So my server shows the text login screen on the attached tft. Systemd messages are logged to this tft by default (I have changend nothing).

Last night logrotate was hanging forever and I figured out why: I accidentally hit the "Scroll Lock" key on the keyboard (or perhaps my cat, I don't know).

I this state, systemctl hangs forever if you try to stop, start, restart or reload a service, I think because of the log messages to the console.

And logrotate was hanging, because of the reload of a service (in my case httpd).

After pressing "Scroll Lock" again, logrotate continued.

Im am running systemd-26-4.fc15.i686.

Comment 1 Lennart Poettering 2011-08-31 00:49:16 UTC
Hmm, C-s/ScrollLock is a command to freeze the application on the console. If you press it, then that's what you get. That is the same with systemd and sysvinit and everything else and is expected behaviour.

If you want to disallow freezing the apps which access the console then remove scrolllock/C-s from your keymap, but I don't think we should try to circumvent the explicit user request here (I don't even think there's a nice way how we even could).

In short: I don't think there's anything we should or could fix here.


Note You need to log in before you can comment on or make changes to this bug.