Hi. After a YOU upgrade and reboot I get: No directory /root! logging in with home="/" -bash: /root/.bash-profile:Permission denied I can ssh into the box with no problem and perform on the remote machine as if I were in total root control. There is no file .bash_profile under /root can anyone help? thanks, Steve.
On Thursday 16 September 2004 10:41 am, steve-ss wrote:
Hi. After a YOU upgrade and reboot I get:
No directory /root! logging in with home="/" -bash: /root/.bash-profile:Permission denied
I can ssh into the box with no problem and perform on the remote machine as if I were in total root control.
There is no file .bash_profile under /root
can anyone help?
thanks, Steve.
So ssh in, create /root, built or copy a .bash-profile therein and bob's you uncle. -- _____________________________________ John Andersen
On Friday 17 September 2004 08:29, John Andersen wrote:
On Thursday 16 September 2004 10:41 am, steve-ss wrote:
Hi. After a YOU upgrade and reboot I get:
No directory /root! logging in with home="/" -bash: /root/.bash-profile:Permission denied
I can ssh into the box with no problem and perform on the remote machine as if I were in total root control.
There is no file .bash_profile under /root
can anyone help?
thanks, Steve.
So ssh in, create /root, built or copy a .bash-profile therein and bob's you uncle.
Sorry but being really thick. /root already exists. There is no .bash_profile to be copied. How would I create it? thanks, Steve.
On Thursday 16 September 2004 10:47 pm, steve-ss wrote:
On Friday 17 September 2004 08:29, John Andersen wrote:
On Thursday 16 September 2004 10:41 am, steve-ss wrote:
Hi. After a YOU upgrade and reboot I get:
No directory /root! logging in with home="/" -bash: /root/.bash-profile:Permission denied
I can ssh into the box with no problem and perform on the remote machine as if I were in total root control.
There is no file .bash_profile under /root
can anyone help?
thanks, Steve.
So ssh in, create /root, built or copy a .bash-profile therein and bob's you uncle.
Sorry but being really thick. /root already exists. There is no .bash_profile to be copied. How would I create it?
thanks, Steve.
But is /root owned by root? Do this: (list dirs by showing numeric uid/gid ls -ln / Then cat /etc/passwd and see if root says something like root:x:0:0:root:/root:/bin/bash The 0:0 bit is the uid/gid, it must match the uid/gid that the ls command gives. -- _____________________________________ John Andersen
On Fri, 2004-09-17 at 02:58, John Andersen wrote:
Sorry but being really thick. /root already exists. There is no .bash_profile to be copied. How would I create it?
thanks, Steve.
But is /root owned by root? Do this: (list dirs by showing numeric uid/gid ls -ln /
Then cat /etc/passwd and see if root says something like root:x:0:0:root:/root:/bin/bash
The 0:0 bit is the uid/gid, it must match the uid/gid that the ls command gives.
Actually root's dir and files should match what /etc/passwd shows which should be 0:0. If you change it to something different you will have problems with root's ability to function. -- Ken Schneider unix user since 1989 linux user since 1994 SuSE user since 1998 (5.2) * PLEASE only reply to the list *
On Friday 17 September 2004 13:07, Ken Schneider wrote:
On Fri, 2004-09-17 at 02:58, John Andersen wrote:
Sorry but being really thick. /root already exists. There is no .bash_profile to be copied. How would I create it?
thanks, Steve.
But is /root owned by root? Do this: (list dirs by showing numeric uid/gid ls -ln /
Then cat /etc/passwd and see if root says something like root:x:0:0:root:/root:/bin/bash
The 0:0 bit is the uid/gid, it must match the uid/gid that the ls command gives.
Actually root's dir and files should match what /etc/passwd shows which should be 0:0. If you change it to something different you will have problems with root's ability to function.
It was indeed the /etc/passwd file that had been corrupted. fortunately I had a backup from a few days ago so it was then just a matter of readding the new users since then. What is more concerning is why it happened just after a YOU. And why could I use ssh from another box on the lan. Thanks to all who spared their time. Steve.
On Friday 17 September 2004 08:55 am, steve-ss wrote:
What is more concerning is why it happened just after a YOU. And why could I use ssh from another box on the lan.
Thanks to all who spared their time. Steve.
As to why you could ssh in, it depends on how you had set up ssh. If you transfer your keys over to the other box from this on, you never need remember roots password at all, as ssh will take care of it via your public/private key pair. -- _____________________________________ John Andersen
participants (3)
-
John Andersen
-
Ken Schneider
-
steve-ss