Linux - GeneralThis Linux forum is for general Linux questions and discussion.
If it is Linux Related and doesn't seem to fit in any other forum then this is the place.
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Introduction to Linux - A Hands on Guide
This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter.
For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own.
Click Here to receive this Complete Guide absolutely free.
I want to be able to boot into level 3 without a keyboard or monitor connected and have the virtual console appear without having to plug in the keyboard. I only want to be able to connect the monitor to see if it is spewing errors or just to take a look at it's hostname. I know i can redirect the spewing errors to a file, but i'd still like to physically only need to connect the monitor to check out the "kernel panic" or "gart errors".
I've tried putting this in rc.local and it didn't work for me on Whitebox 3.0
setterm -blank 0 -powersave off -powerdown 0 > tty1
I've also tried setterm with with only one of the three options
It work fines if your keyboard is already plugged in and you do it at virtual console 1 and unplug your keyboard. It seems like it only works if the keyboard is plugged into the system to begin with.
On that note, how could i make a script or cron that will send the signal of a keyboard plugged in or the signal of the shift key being pressed without actually using a physical keyboard present. It would be a nice little trick.
I haven't gotten the chance to try it out yet. So you are echoing the ESC character and what is the [9;0] part? How would that disable the screen blanking? I thought setterm -blank 0 does that? Or are you just doing another method to disable the screen? By the the way, thanks for the reply.
Have you tried just doing 'setterm -blank 0 -powersave off -powerdown 0' without redirecting to tty1. The problem is that rc.local is run just before switching to runlevel 3, i.e. before the getty's are started, before tty1 is opened, so it would have no effect (I think).
ioerror is right - if you are booting to runlevel 3, the ttys have not been started at the point that the init scripts are running. What you will have to do is modify /etc/inittab to have the first mingetty autologin a user:
I thought about putting it in the inittab, but i realized I'd have to setterm for a specific user. I think setterm is reset after every respawn or if you logout. I tried doing setterm without directing to tty1 first, and that didn't work.
By using autologin, wouldn't that be less secure? I guess I could create a very limited account, but i'd like to keep it so no user is auto logged in at all.
Does using --autologin still give you a login prompt? I am guessing no and it brings you to a prompt.
Another question, lets say I do setup the autologin, does that mean I cannot log out since i I want my setterm setting to still not blank the screen?
I'd really like to have a way that would not depend on user and just not blank the screen so only a monitor is needed to view the screen output.
Thanks for the input, really appreciate it. I'm trying to set this up on several hundred systems and it gets annoying that (1) gotta plug in the kb (2) if the system crashed, it doesn't respond to kb (3) viewing the last moments before the crash would be great in diagnosing.
Using 1:2345:respawn:/sbin/mingetty --autologin username tty1 along with the code above. As soon as the autologin logs in, it exits just as the .bash_profile says and respawns again till it respawns too many times and gets a 5 minute lock out. I guess it's natural for it to respawn since it was told to do so.
I want to still be able to login to the console and have it respawn after loggin out.
My question is since the code you have give me logs me out, doesn't the setterm command reset to defaults...making an autologin account not necessary since it gets reset after log out?