HPE GreenLake Administration
- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- Re: Workstation boots up in single user mode ?
Operating System - HP-UX
1841357
Members
2035
Online
110179
Solutions
Forums
Categories
Company
Local Language
back
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Forums
Discussions
Discussions
Discussions
Forums
Discussions
back
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
- BladeSystem Infrastructure and Application Solutions
- Appliance Servers
- Alpha Servers
- BackOffice Products
- Internet Products
- HPE 9000 and HPE e3000 Servers
- Networking
- Netservers
- Secure OS Software for Linux
- Server Management (Insight Manager 7)
- Windows Server 2003
- Operating System - Tru64 Unix
- ProLiant Deployment and Provisioning
- Linux-Based Community / Regional
- Microsoft System Center Integration
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Blogs
Information
Community
Resources
Community Language
Language
Forums
Blogs
Topic Options
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-28-2000 02:02 PM
04-28-2000 02:02 PM
Workstation boots up in single user mode ?
Hi,
When I startup the workstation, it boots up in single user mode only. The
following message is displayed
INIT: SINGLE USER MODE
INIT: WARNING: Bad shell "/usr/bin/sh" for root.
FIX root ENTRY IN /etc/passwd AND REBOOT !!!
At the command prompt,
#who ( it gives the sh: who: not found.
#who -r ( the same message sh: who: not found.)
When I tried to edit the passwd file using vi in the /etc folder, sh: vi not
found message is displayed.
I can use #cat passwd ( to the see the content of the file).
Is there any other way to edit the passwd file other than vi.
I cannot access sam also. What should i do to fix the problem or only option is
to re-install the os.
Appciate your reply.
Thanks.
Sailesh.
When I startup the workstation, it boots up in single user mode only. The
following message is displayed
INIT: SINGLE USER MODE
INIT: WARNING: Bad shell "/usr/bin/sh" for root.
FIX root ENTRY IN /etc/passwd AND REBOOT !!!
At the command prompt,
#who ( it gives the sh: who: not found.
#who -r ( the same message sh: who: not found.)
When I tried to edit the passwd file using vi in the /etc folder, sh: vi not
found message is displayed.
I can use #cat passwd ( to the see the content of the file).
Is there any other way to edit the passwd file other than vi.
I cannot access sam also. What should i do to fix the problem or only option is
to re-install the os.
Appciate your reply.
Thanks.
Sailesh.
3 REPLIES 3
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-28-2000 10:21 PM
04-28-2000 10:21 PM
Re: Workstation boots up in single user mode ?
Hi sailesh,
The default shell for the super user is /sbin/sh.
The reason is that when the system comes up ,it start
a temporary shell and execcutes all other functions, at this time only the
root file system will be mounted .All other File systems gets mounted after
running /sbin/rc .
So copy /usr/bin/sh to /sbin/sh and change the
shell path in /etc/passwd to /sbin/sh.This will solve this problem.
This happens to the systems installed with /usr
as a separated filesystem.
Rajesh.TT
Bangalore
The default shell for the super user is /sbin/sh.
The reason is that when the system comes up ,it start
a temporary shell and execcutes all other functions, at this time only the
root file system will be mounted .All other File systems gets mounted after
running /sbin/rc .
So copy /usr/bin/sh to /sbin/sh and change the
shell path in /etc/passwd to /sbin/sh.This will solve this problem.
This happens to the systems installed with /usr
as a separated filesystem.
Rajesh.TT
Bangalore
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-29-2000 10:14 AM
04-29-2000 10:14 AM
Re: Workstation boots up in single user mode ?
STOP, DONT DO THE COPY AS SUGGESTED!
If you copy shells over, when you upgrade or patch, it never gets patched.
If you wish to use vi
#/sbin/mount -a
This will mount all the filesystems so that you can
use vi and find it in your search path.
then edit passwd file and change roots shell to
/sbin/sh or even /usr/bin/ksh works
Else
about the only thing left is awk. but I would not recommend it.
If you are inteerested in the commands available to you in single user mode,
Regards
Terja
If you copy shells over, when you upgrade or patch, it never gets patched.
If you wish to use vi
#/sbin/mount -a
This will mount all the filesystems so that you can
use vi and find it in your search path.
then edit passwd file and change roots shell to
/sbin/sh or even /usr/bin/ksh works
Else
about the only thing left is awk. but I would not recommend it.
If you are inteerested in the commands available to you in single user mode,
Regards
Terja
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-12-2000 08:39 AM
05-12-2000 08:39 AM
Re: Workstation boots up in single user mode ?
I agree with not copying /usr/bin/sh to /sbin/sh, but not the reasoning.
It has always been my assumption that the reason not to copy /usr/bin/sh to /sbin/sh is that the shells differ greatly. Mainly that /sbin/sh is statically linked, and /usr/bin/sh is dynamically linked. At init time, the shell would not be able to find libraries, then not function.
Please correct me if I am wrong!
PS Many New HP Admins make the mistake of changing the root shell. It is OK in SunOS, Irix, and AIX.
It has always been my assumption that the reason not to copy /usr/bin/sh to /sbin/sh is that the shells differ greatly. Mainly that /sbin/sh is statically linked, and /usr/bin/sh is dynamically linked. At init time, the shell would not be able to find libraries, then not function.
Please correct me if I am wrong!
PS Many New HP Admins make the mistake of changing the root shell. It is OK in SunOS, Irix, and AIX.
Microsoft. When do you want a virus today?
The opinions expressed above are the personal opinions of the authors, not of Hewlett Packard Enterprise. By using this site, you accept the Terms of Use and Rules of Participation.
Company
Events and news
Customer resources
© Copyright 2025 Hewlett Packard Enterprise Development LP