Ian Bell wrote:

> On the same subject I just set up slack 10 to use kdm as the login
> manager rather than a console login followed by startx. Works fine for
> root but any other user gets a message 'your shell is not listed in
> /etc/shells'.**This*file*contains*a*list*with*entries*l ike*/bin/bash.
> Any*idea*what*the*problem*is?

Some applications that manage logins require that the user's "shell" be a
"valid" one. The shell is the program that provides your user interface in
console mode. To be "valid" just means that it is listed in /etc/shells.

It is odd to have a user without a valid shell, and it makes me wonder how
you created that user. In any case though, to fix it, you'll need to log in
as root, and open a terminal application (like konsole, if you're using
KDE).

To see what shell a user has (and other info), run the command:

# finger <username>

(Substitute a real username for <username>). A typical valid shell is
"/bin/bash", and to set the user's shell to that you could run the command:

# usermod -s /bin/bash <username>

After that you should be able to log in as that user, using KDM.

Hope that helps,
Jeffrey

Rich Grise <null@example.net> wrote:
> Symlink?

Yes, see my example.

--
/* - =- = -=-=-=- Variant -=-=-=- = -= - */
/* v a r i a n t @ r o o t s h e l l . b e */
/* - =- = -=-=- - --===-- - -=-=- = -= - */

Jeffrey Froman wrote:
> Ian Bell wrote:
>
>
>>On the same subject I just set up slack 10 to use kdm as the login
>>manager rather than a console login followed by startx. Works fine for
>>root but any other user gets a message 'your shell is not listed in
>>/etc/shells'. This file contains a list with entries like /bin/bash.
>>Any idea what the problem is?
>
>
> Some applications that manage logins require that the user's "shell" be a
> "valid" one. The shell is the program that provides your user interface in
> console mode. To be "valid" just means that it is listed in /etc/shells.
>
> It is odd to have a user without a valid shell, and it makes me wonder how
> you created that user. In any case though, to fix it, you'll need to log in
> as root, and open a terminal application (like konsole, if you're using
> KDE).
>
> To see what shell a user has (and other info), run the command:
>
> # finger <username>
>
> (Substitute a real username for <username>). A typical valid shell is
> "/bin/bash", and to set the user's shell to that you could run the command:
>
> # usermod -s /bin/bash <username>

For some reason it was set to /bin/sh which is symlinked to /bin/bash.
I used kuser to set up the user. /bin/sh is its default shell
setting. I have changed it now the /bin/bash so I'll try again.
Thanks for the help.


--
Ian Bell

Ian Bell wrote:
> Jeffrey Froman wrote:
>
>> Ian Bell wrote:
>>
>>
>>> On the same subject I just set up slack 10 to use kdm as the login
>>> manager rather than a console login followed by startx. Works fine for
>>> root but any other user gets a message 'your shell is not listed in
>>> /etc/shells'. This file contains a list with entries like /bin/bash.
>>> Any idea what the problem is?
>>
>>
>>
>> Some applications that manage logins require that the user's "shell" be a
>> "valid" one. The shell is the program that provides your user
>> interface in
>> console mode. To be "valid" just means that it is listed in /etc/shells.
>>
>> It is odd to have a user without a valid shell, and it makes me wonder
>> how
>> you created that user. In any case though, to fix it, you'll need to
>> log in
>> as root, and open a terminal application (like konsole, if you're using
>> KDE).
>>
>> To see what shell a user has (and other info), run the command:
>>
>> # finger <username>
>>
>> (Substitute a real username for <username>). A typical valid shell is
>> "/bin/bash", and to set the user's shell to that you could run the
>> command:
>>
>> # usermod -s /bin/bash <username>
>
>
> For some reason it was set to /bin/sh which is symlinked to /bin/bash.
> I used kuser to set up the user. /bin/sh is its default shell setting.
> I have changed it now the /bin/bash so I'll try again. Thanks for the help.
>
>

That worked fine. For some reasin /bin/sh is not listed in
/etc/shells but I have added it to avoid the same problem in future.

Ian

--
Ian Bell