All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ray Olszewski <ray@comarre.com>
To: linux-newbie@vger.kernel.org
Subject: Re: Cannot login as non-root user
Date: Tue, 15 Jul 2003 19:25:34 -0700	[thread overview]
Message-ID: <5.1.0.14.1.20030715191243.01fcece8@celine> (raw)
In-Reply-To: <20030715.162201.505.419099@webmail10.lax.untd.com>

See below.

At 11:21 PM 7/15/2003 +0000, beolach@juno.com wrote:

>On my brother's computer, running Slackware 9.0, we have just recently
>begun experiencing problems signing in as non-root users, either from
>normal login, su, su -, or ssh.  After entering username & password,
>login prints the error "Cannot execute /bin/bash: Permission denied"
>and returns to login prompt. Su & su - from root prints the same error,
>"Cannot execute /bin/bash: Permission denied" and returns to the root
>shell.  Ssh gives "/bin/bash: Permission denied" and connection lost.
>Root can sign in with no problems at all.
>
>The first thing I did was check the pemissions on /bin/bash, and it
>is executable for everyone: -rwxr-xr-x.  We've also un/reinstalled
>the bash package (we've tried the bash packages from both the
>slackware-9.0 and slackware-current distributions; bash-2.05b-i386-2
>and bash-2.05b-i486-3), with no change.  I've also removed & readded
>the user accounts in /etc/passwd & /etc/shadow, both with vipw and
>userdel/useradd; again with no result.
>
>We started experiencing this quite suddenly, while we were trying to
>get X setup with 3d acceleration for my brothers ATI Radeon 9500 Pro
>(which is still not working, anyone here have experience?), and I am
>have no idea what started the login problems, because obviously X has
>nothing to do with login, and we really weren't doing anything else.
>
>Any help resolving this is greatly appreciated,
>Conway S. Smith

Basic questions:

1. What is root's shell? Is it /bin/bash or /bin/sh? (If the latter, is 
/bin/sh a symlink to /bin/bash? It usually is but might not be in your case.)

2. What are permissions on /bin? They should be 755 (rwxr-xr-x).

3. This feels like a long shot, but might there be a permissions problem 
with one of the shared libraries bash uses? Check your system with "ldd 
/bin/bash". Mine shows these libraries involved:

         autovcr@kuryakin:~$ ldd /bin/bash
                         libncurses.so.5 => /lib/libncurses.so.5 (0x40018000)
                         libdl.so.2 => /lib/libdl.so.2 (0x40055000)
                         libc.so.6 => /lib/libc.so.6 (0x40058000)
                         /lib/ld-linux.so.2 => /lib/ld-linux.so.2 (0x40000000)

4. Another long shot: how full is /var ? /tmp ? / ? Might bash be unable to 
create a log or scratch file, or login a wtmp entry, as an ordinary user 
that it can as root (since root can use reserved areas of filesystems)?

5. And another: might some filesystem be mounted read only?

6. This sounds very non-Linux, but ... have you rebooted? It's just barely 
possible that some kernel pointer got corrupted somehow and you need to 
reload a fresh kernel to get the permissions read properly.

If none of this gets you anywhere, and no one else comes up with something 
better, next time tell us in more detail waht you have been doing to get X 
working. Just editing XF86Config-4? Or fiddlign with other parts of the 
system too?



-
To unsubscribe from this list: send the line "unsubscribe linux-newbie" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.linux-learn.org/faqs

  parent reply	other threads:[~2003-07-16  2:25 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-07-15 23:21 Cannot login as non-root user beolach
2003-07-15 23:48 ` Puneet B
2003-07-16  0:30 ` Alan Bort
2003-07-16  2:25 ` Ray Olszewski [this message]
2003-07-16  3:01 beolach
2003-07-16  9:49 ` Michael Scottaline

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=5.1.0.14.1.20030715191243.01fcece8@celine \
    --to=ray@comarre.com \
    --cc=linux-newbie@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.