topic Re: login problem in Operating System - HP-UX

login problem

yatin — Wed, 21 Apr 2004 01:21:05 GMT

I made some changes to /etc/passwd now I get error message as NO SHELL I was using root a/c
and I donot have any other a/c

Re: login problem

Clemens van Everdingen — Wed, 21 Apr 2004 01:23:33 GMT

Hi,

Did you change by accident the shell for the root user to /sbin/ksh instead of /sbin/sh ?

If yes you need to reboot the system into single user mode and correct this.

C.

Re: login problem

V.Tamilvanan — Wed, 21 Apr 2004 01:36:21 GMT

Hi,
You need to cold restart the system and boot through single user mode by using hpux -is on ISL prompt and copy back your old passwd file or add the entry /sbin/sh at the Shell entry in /etc/passwd file.

Re: login problem

Michael Tully — Wed, 21 Apr 2004 01:37:39 GMT

DO NOT REBOOT your system. You need to put the entry back. The entry *must* read as /sbin/sh as the shell. Nothing else will work.

Re: login problem

KapilRaj — Wed, 21 Apr 2004 01:42:56 GMT

U have changed the root user's shell;

Undo the changes and put it back as it was

Regds,

Kaps

Re: login problem

Roberto Polli — Wed, 21 Apr 2004 02:23:22 GMT

Michael ,
on my hpux I use /usr/bin/ksh as root shell, and it works.
Sure I agree with you that /sbin/sh can be a better choiche but I neve had problem, even on hd failure, using such a shell.

Peace, R.

Re: login problem

Elmar P. Kolkman — Wed, 21 Apr 2004 02:43:39 GMT

DO NOT USE /usr/... as a shell !!!

You won't be able to boot in LVM maintenance mode. If you want to use a /usr/... program as a shell for root, put something like this in his .profile:
[ -x /usr/bin/ksh ] && exec /usr/bin/ksh

That way, if /usr is not (yet) mounted, you have at least a working root account.

As for the problem itself: it might be a change to the shell of the user that is caused by putting a colon (:) extra on or removing a colon from a line... Make sure the first line looks right, having the right number of colons. And of course a correct executable shell.

Re: login problem

SANTOSH S. MHASKAR — Wed, 21 Apr 2004 05:28:32 GMT

Hi Yatin,

It is a bad practice to edit /etc/passwd if u r a novice. Just change the shell to /sbin/sh by editing /etc/passwd.

Roberto any shell will work but the thing is it should exist.

-Santosh

Re: login problem

SS_6 — Wed, 21 Apr 2004 15:10:41 GMT

Hi Yatin,What I uderstand is you are not able to login to system at all so there is no question of changing anything unless you log into the system.
Try rebooting system in single user mode and make shell chnages to passwd file for root user.

Re: login problem

A. Clay Stephenson — Wed, 21 Apr 2004 16:50:59 GMT

Roberto, I assure you that you did not change root's shell (Here I am assuming that root is UID 0) and boot sucessfully. First of all, /usr would not even be mounted at boot. Now you might have done an exec /usr/bin/ksh in root's .profile but that is different. The fundmental problem is that a statically linked version of the shell must be available for the times before the other filesystems are mounted. /sbin/sh is a fully functional version of the POSIX shell; /usr/bin/sh is a dynamically linked version of the same shell and it used by other users to save memory.

It would be possible to create a statically linked version of ksh or bash and make an entry in /etc/shells and install them in /sbin.

Most people do this out of the mistaken belief the /sbin/sh is a Bourne shell; it is instead a fully functional POSIX shell which is for all intents and purposes a Korn shell.

Re: login problem

Steve Lynn — Wed, 21 Apr 2004 18:35:57 GMT

Goto /etc/default/passwd copy this default login file to /etc/passwd and change passwd for root.

This will enable the correct shell as built by HP

PS.
Create another account with root privs

Regards

Steve

Re: login problem

generic_1 — Wed, 21 Apr 2004 19:48:24 GMT

You can use sam if you are a novice and then go look at the sam logs to see what commands it ran. You could also compare an old copy to the new in additoin to your reading of the man pages. Before editing the password file in the future you may want to consider cp /etc/passwd /etc/passwd.old just in case. This is a good practice whenever editing almost any kind of file.