Submit Hint Search The Forums LinksStatsPollsHeadlinesRSS
14,000 hints and counting!

Exit >console mode cleanly and easily Desktop
Many of you may already know this from other unices as a way to exit the shell, but for those that don't ... Control-D will work to exit the >console mode as well. However, I've noticed a tendency for the system (Jag 10.2.x) to hang a bit if the key combo is executed immediately (within one to three seconds) after entering >console mode. The login GUI eventually appears, however.
    •    
  • Currently 3.00 / 5
  You rated: 5 / 5 (2 votes cast)
 
[7,648 views]  

Exit >console mode cleanly and easily | 8 comments | Create New Account
Click here to return to the 'Exit >console mode cleanly and easily' hint
The following comments are owned by whoever posted them. This site is not responsible for what they say.
The delay is normal
Authored by: Auricchio on Jan 17, '03 11:40:15AM

If you type CTL-D immediately, you are doing so to the login: prompt. The CTL-D (end-of-file) causes getty to exit. Init then has to catch the termination, check /etc/gettydefs, and spawn a new getty process.

On many systems, there is a deliberate delay to slow down repeated attempts to login by password guesses. This may be the case here, or you\'re just seeing the turnaround time to wake up init and spawn the new getty process.



[ Reply to This | # ]
Exit >console mode cleanly and easily
Authored by: bmcgill on Jan 23, '03 02:52:23PM
Some of you get it. Others, let me be more specific... When entering >console mode (at gui login enter >console for the name with blank password), you are greeted with a command line login prompt. Normally, "exit" or "logout" would work if you were logged in. But you're not. So, this is how you exit back to the gui login without having to login first . The only other way is either physically rebooting or failing the login 9 times (hmm... I wonder if there is a way to change this number? Anyone?).

[ Reply to This | # ]
Umm, why not just 'exit'?
Authored by: klktrk on Jan 17, '03 12:31:50PM

Am I missing something here? The proper way to exit a console or terminal session is and has always been to simply type 'exit' and hit return. The exit command saves your command history to your .tcsh_history file, so you can scroll through them at a later session, checks for running background processes and shuts down any other resources associated with your session cleanly and quickly. It does this in about a half a second. Why anybody would exit a console or terminal session any other way is beyond me.



[ Reply to This | # ]
Umm, why not just 'exit'?
Authored by: klktrk on Jan 17, '03 12:36:57PM

I ought to be spanked.



[ Reply to This | # ]
Umm, why not just 'exit'?
Authored by: bjackson on Jan 17, '03 05:35:38PM

I believe the shell traps ctrl-D and does an exit - i.e.; you're doing the same thing.

Brian



[ Reply to This | # ]
How about 'logout'?
Authored by: Titanium Man on Jan 17, '03 01:33:16PM

I've always typed 'logout'. That's what I use on other "Unix-like operating systems" as well. But maybe there's a better way?



[ Reply to This | # ]
timely hint, am dumped to console
Authored by: bradhenry on Jan 17, '03 03:08:13PM

A timely hint for me, thanks. If I type my password incorrectly I am dumped to the console login. I've been doing ctrl-D immediately and have noticed the hang. Now I will wait a bit, thanks!
Of course I could investigate why I am being dumped to console when my password is incorrect, but that seems like too much effort.



[ Reply to This | # ]
timely hint, am dumped to console
Authored by: cgull on Jan 20, '03 09:06:38PM

I just noticed the same thing (about 10 minutes before reading the above post), but it's probably because my 6 yr. old daughter had been using my wife's computer for an hour or so. (who knows what they REALLY are doing)

She had logged out somehow and while I was logging her in (I guess she had clicked on "other" in the login window) I clicked in the 'name'field, and as soon as I hit TAB it bumped me into console. This happened repeatedly. I had to tell it to reboot in console.



[ Reply to This | # ]