1 |
On Fri, Feb 13, 2009 at 3:05 AM, Dale <rdalek1967@×××××.com> wrote: |
2 |
> Hi folks, |
3 |
> |
4 |
> I from time to time will go to a console and do a rc single to go to |
5 |
> single user mode. I have noticed something weird when I go back to rc |
6 |
> default tho. On the #1 console, it acts and looks like I am logged out |
7 |
> but when I type in the user name root, it acts like it is a command. |
8 |
> Same with the password. However, if I just type in a command, it spits |
9 |
> that back out too. It doesn't seem to like a login or a command. |
10 |
> |
11 |
> It did this a bit ago. I just typed in junk and let it reach the bad |
12 |
> login limit and reset the console. It then gave me a login and let me |
13 |
> do a legitimate login. It cleared the screen which is what is in |
14 |
> .bash_login so I know I am logged in. |
15 |
> |
16 |
> This is just sort of weird to me. The screen when it gets through |
17 |
> starting services looks just like it does when I reboot. I see the last |
18 |
> few services at the top then my login prompt at the bottom. Everything |
19 |
> looks normal but it's not. What can I check? Is this normal? When I |
20 |
> type in rc default should something reset tty1 so that a new login is |
21 |
> required? It acts like it is still logged in as root which could be a |
22 |
> security problem for some. Just curious really. |
23 |
> |
24 |
> Dale |
25 |
> |
26 |
> :-) :-) |
27 |
|
28 |
Sounds like it's not closing out of the existing shell on the terminal |
29 |
but is till starting a login process on top of it. The lazy fix is to, |
30 |
when you go single user, throw a " & logout" on the end of the command |
31 |
to make sure the shell closes out. |
32 |
|
33 |
If you want to poke around and see, for certain, that it is doing what |
34 |
I'd guess it is.. change your inittab and add another login in single |
35 |
user mode on tty2, log in, and check "w" for an active session on |
36 |
another tty. |
37 |
|
38 |
-- |
39 |
Poison [BLX] |
40 |
Joshua M. Murphy |