| 1 |
On Fri, 13 Feb 2009 15:43:49 +0800 |
| 2 |
Chuanwen Wu <wcw8410@×××××.com> wrote: |
| 3 |
|
| 4 |
> Hi, here is the root infomation in my /etc/passwd: |
| 5 |
> root:x:0:0:root:/root:/bin/bash |
| 6 |
|
| 7 |
Looks okay, can't see anything wrong in bash configs, too. |
| 8 |
|
| 9 |
|
| 10 |
> I got the login information below from the tail of /var/log/messages: |
| 11 |
... |
| 12 |
|
| 13 |
I believe this clearly shows that pam shouldn't be the issue, but |
| 14 |
something that gets launched (and that should be shell) is. |
| 15 |
|
| 16 |
I don't know if there are any issues with bash and I rarely use it |
| 17 |
myself (only as a login shell on debian machines, 'cause they have it |
| 18 |
on root, installing zsh to usr), but prehaps there are in some bugzilla. |
| 19 |
|
| 20 |
Also, I can assume that getty somehow fails to launch /bin/login |
| 21 |
correctly or /bin/login somehow fails. |
| 22 |
You can check that getty (agetty, in gentoo), not something else, gets |
| 23 |
launched from /etc/inittab and recompile it, just in case. |
| 24 |
Then you can try recompiling the shadow package, since /bin/login, which |
| 25 |
should launch the shell belongs to it. |
| 26 |
|
| 27 |
You can also check if it's possible to make agetty run something else, |
| 28 |
then /bin/login (should be), and launch 'strace /bin/login' instead, |
| 29 |
or just run agetty through 'strace -f', which'll show you all the kernel |
| 30 |
calls it uses and if there are any failures. |
| 31 |
I've found some obscure mistakes (my mistakes, always) that way, but it |
| 32 |
might be quite time-consuming. |
| 33 |
|
| 34 |
|
| 35 |
-- |
| 36 |
Mike Kazantsev // fraggod.net |
Archives