Bug 170488
Summary: | "screen" support would be good | ||
---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Need Real Name <lsof> |
Component: | vlock | Assignee: | Karel Zak <kzak> |
Status: | CLOSED RAWHIDE | QA Contact: | |
Severity: | medium | Docs Contact: | |
Priority: | medium | ||
Version: | 4 | ||
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2005-10-14 12:19:20 UTC | Type: | --- |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Need Real Name
2005-10-12 10:10:52 UTC
*** This tty is not a VC (virtual console). *** *** It may not be securely locked. *** This TTY is now locked. Please enter the password to unlock. root's Password: Do you think that the sentence "It may not be securely locked." is not enough? Well, I can add there some next extra message like "You're probably runnig screen(1). Please, check screen documentation for correct locking.". But I think the the actual warning is almost enough. The message "it may not be securely locked" shows when you try to lock a virtual console, but the docs say this message appears because virtual console locking has been given less testing than real console locking. When I run vlock from inside screen, the console is *definitely* not securely locked - I can run ^AC to create a new console. A screen specific warning would be good I think. Done. Update to vlock-1.3-22. Note that fixed in the development branch (FC5). Thanks! |