01-24-2012
If you are still working with this, try "enable tty01" as root, it seems like someone turned off the character based console logins.
10 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
Hello all,
1) I want to have a GUI application that will call Unix shell scripts,
2) that GUI application should be able to reside on windows ( if possible) and then call Unix shell script either directly or through a server residing on unix.
That is for example.
If a is windows gui (... (1 Reply)
Discussion started by: hchivukula
1 Replies
2. UNIX for Dummies Questions & Answers
:) Hi everybody..
This is my firt post in this great forum.:
I have installed Sun Solaris 10 on an Intel machine..
Now i login in CDE desktop as root.
I want to switch between terminal screens pressing CTRL+ALT F1 (through F6) but nothing happens ??
any suggestions
thank you (2 Replies)
Discussion started by: peterpan
2 Replies
3. AIX
Can I know is there anyone know how to statup AIX in GUI and text mode?
Thank You..... (2 Replies)
Discussion started by: dwarf007
2 Replies
4. Shell Programming and Scripting
Hello,
I have written some scripts that query the user and waits for keyboard input for an answer. I was wondering if there is any generic code snippets out there that would allow me to run this as a GUI. I am thinking of a simple dialogue box that would display the question and have a text... (1 Reply)
Discussion started by: Allasso
1 Replies
5. Solaris
Hi all
I have installed solaris 5.10 and it is loading in GUI mode by default.
I want to load in text mode by default. How to do this? How to switch from GUI to text mode and vise versa.?
Please help.. (2 Replies)
Discussion started by: johnl
2 Replies
6. Windows & DOS: Issues & Discussions
jEdit, Total Edit, EDXOR, all have one thing in common -- whatever they save in what they call "Unix" encoding and line endings inevitably shows up in a CLI text editor like pico or vim having garbage characters somewhere close to the beginning or, though this is more rare, somewhere in the body of... (0 Replies)
Discussion started by: SilversleevesX
0 Replies
7. HP-UX
How I can I remove the welcome screen for HPUX
ie
* *
* *
* Welcome to AIX Version 5.3! *
* *
but only for some users ?
Thanks (4 Replies)
Discussion started by: belfastbelle
4 Replies
8. Hardware
Dear All,
i am trying to install the redhat linux using graphical mode...but it stucks while probing video card...i have installed linux using text mode it works fine and whole the installation goes fine. after installation if i give startx command it again stucks....looks like a vga card... (9 Replies)
Discussion started by: zaheer.gr8
9 Replies
9. Red Hat
Hi folks,
I was running many commands using root and closed the session.
I would like to see if there is a way to go back to the server and see those screens so I can remember what I did the next time I need to do that.
Thanks a bunch! (3 Replies)
Discussion started by: 300zxmuro
3 Replies
10. Programming
python gui or c++ gui or java gui?
and when to use etch one? (1 Reply)
Discussion started by: kaja
1 Replies
LEARN ABOUT X11R4
pam_securetty
PAM_SECURETTY(8) Linux-PAM Manual PAM_SECURETTY(8)
NAME
pam_securetty - Limit root login to special devices
SYNOPSIS
pam_securetty.so [debug]
DESCRIPTION
pam_securetty is a PAM module that allows root logins only if the user is logging in on a "secure" tty, as defined by the listing in
/etc/securetty. pam_securetty also checks to make sure that /etc/securetty is a plain file and not world writable. It will also allow root
logins on the tty specified with console= switch on the kernel command line and on ttys from the /sys/class/tty/console/active.
This module has no effect on non-root users and requires that the application fills in the PAM_TTY item correctly.
For canonical usage, should be listed as a required authentication method before any sufficient authentication methods.
OPTIONS
debug
Print debug information.
noconsole
Do not automatically allow root logins on the kernel console device, as specified on the kernel command line or by the sys file, if it
is not also specified in the /etc/securetty file.
MODULE TYPES PROVIDED
Only the auth module type is provided.
RETURN VALUES
PAM_SUCCESS
The user is allowed to continue authentication. Either the user is not root, or the root user is trying to log in on an acceptable
device.
PAM_AUTH_ERR
Authentication is rejected. Either root is attempting to log in via an unacceptable device, or the /etc/securetty file is world
writable or not a normal file.
PAM_INCOMPLETE
An application error occurred. pam_securetty was not able to get information it required from the application that called it.
PAM_SERVICE_ERR
An error occurred while the module was determining the user's name or tty, or the module could not open /etc/securetty.
PAM_USER_UNKNOWN
The module could not find the user name in the /etc/passwd file to verify whether the user had a UID of 0. Therefore, the results of
running this module are ignored.
EXAMPLES
auth required pam_securetty.so
auth required pam_unix.so
SEE ALSO
securetty(5), pam.conf(5), pam.d(5), pam(7)
AUTHOR
pam_securetty was written by Elliot Lee <sopwith@cuc.edu>.
Linux-PAM Manual 09/19/2013 PAM_SECURETTY(8)