On Mon, 08 Dec 2008 08:30:54 -0500
michael <[EMAIL PROTECTED]> wrote:
> > does remote machine have ipmi?
indeed..or iLO or serial console... you'd be surprised the number of dedicated
servers on offer that don't have any out of band access available... i guess
it's the option everyone wants once
J
On Sun, Dec 07, 2008 at 11:04:00AM +0100, Redd Vinylene wrote:
On this dedicated box here I made the mistake of adding a comment to
root's entry in my password file:
root:*:0:0::/root:/bin/sh # What I thought would be a harmless comment.
Now I can't su to root. And my ISP is closed on
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Michael Powell wrote:
> I've never figured out why people seem to always want to play with the
> root account the way they do, such as the favorite "I wanna use bash
> for root's shell"...
Probably because most users are unaware of the harm that it c
If so, force it to reboot - maybe by pulling the plug if you have to
then bring it up in single user mode.
CTRL-ALT-DEL shutdowns the system unless it was configured not to.
Remount root mount -u /
Then use vipw to edit the file and remove that comment and any trailing
blanks on that lin
On Sun, Dec 07, 2008 at 11:04:00AM +0100, Redd Vinylene wrote:
> On this dedicated box here I made the mistake of adding a comment to
> root's entry in my password file:
>
> root:*:0:0::/root:/bin/sh # What I thought would be a harmless comment.
>
> Now I can't su to root. And my ISP is closed o
On Sun, December 7, 2008 11:04, Redd Vinylene wrote:
> On this dedicated box here I made the mistake of adding a comment to
> root's entry in my password file:
>
> root:*:0:0::/root:/bin/sh # What I thought would be a harmless comment.
>
> Now I can't su to root. And my ISP is closed on Sundays. Is
Ruben de Groot wrote:
[snip]
>
> This advise is only helpful if you have root allready =)
I've never figured out why people seem to always want to play with the
root account the way they do, such as the favorite "I wanna use bash
for root's shell"...
Since the OP seems to want to keep playing w
On Sun, Dec 07, 2008 at 06:02:26AM -0500, Michael Powell typed:
> Redd Vinylene wrote:
>
> > Thanks guys. But I guess I'm all outta luck:
> >
> > $ sudo -s
> > /libexec/ld-elf.so.1: Shared object "libutil.so.5" not found, required by
> > "sudo"
> >
> [snip]
>
> Don't know if this would help but
Redd Vinylene wrote:
> Thanks guys. But I guess I'm all outta luck:
>
> $ sudo -s
> /libexec/ld-elf.so.1: Shared object "libutil.so.5" not found, required by
> "sudo"
>
[snip]
Don't know if this would help but you might try creating a file called
libmap.conf in /etc and place in it:
libutil.so
Thanks guys. But I guess I'm all outta luck:
$ sudo -s
/libexec/ld-elf.so.1: Shared object "libutil.so.5" not found, required by "sudo"
On Sun, Dec 7, 2008 at 11:07 AM, Glen Barber <[EMAIL PROTECTED]> wrote:
> On Sun, Dec 7, 2008 at 5:04 AM, Redd Vinylene <[EMAIL PROTECTED]> wrote:
>> On this ded
On Sun, Dec 7, 2008 at 5:04 AM, Redd Vinylene <[EMAIL PROTECTED]> wrote:
> On this dedicated box here I made the mistake of adding a comment to
> root's entry in my password file:
>
> root:*:0:0::/root:/bin/sh # What I thought would be a harmless comment.
>
This is why you shouldn't edit password
On Sun, Dec 7, 2008 at 12:04 PM, Redd Vinylene <[EMAIL PROTECTED]>wrote:
> On this dedicated box here I made the mistake of adding a comment to
> root's entry in my password file:
>
> root:*:0:0::/root:/bin/sh # What I thought would be a harmless comment.
>
> Now I can't su to root. And my ISP is
On this dedicated box here I made the mistake of adding a comment to
root's entry in my password file:
root:*:0:0::/root:/bin/sh # What I thought would be a harmless comment.
Now I can't su to root. And my ISP is closed on Sundays. Is there any
way I can fix this on my own?
Thanks y'all!
--
ht
On Tue, 2008-09-02 at 03:45 +, adrian wrote:
Hi all this is my first question on the list.
>
> I had been playing with securelevels and was in level 3 then I mistakenly
> executed "chflags schg /etc/rc.*"
> It wouldn't be such a problem but it as you guessed is on a remote server
> and I could
Hi all this is my first question on the list.
I had been playing with securelevels and was in level 3 then I mistakenly
executed "chflags schg /etc/rc.*"
It wouldn't be such a problem but it as you guessed is on a remote server
and I could pay a local guy there to drop to single-user but I thought
can't run "su." I get the following error:
> > >
> > > $ su -
> > > su: not running setuid
> > >
> > > I can't shutdown since I can't become root, so I pulled the plug and
> > > rebooted into single-user mode. I
; >
> > I can't shutdown since I can't become root, so I pulled the plug and
> > rebooted into single-user mode. I edited /etc/rc.conf and set
> > kern_securelevel_enable="NO"
> >
> > I rebooted again, but for some reason I still get the same err
un "su." I get the following error:
>
> $ su -
> su: not running setuid
>
> I can't shutdown since I can't become root, so I pulled the plug and
> rebooted into single-user mode. I edited /etc/rc.conf and set
> kern_securelevel_enable="NO"
>
>
t; I get the following error:
>
> $ su -
> su: not running setuid
>
> I can't shutdown since I can't become root, so I pulled the plug and
> rebooted into single-user mode. I edited /etc/rc.conf and set
> kern_securelevel_enable="NO"
>
> I rebooted again,
dited /etc/rc.conf and set
> kern_securelevel_enable="NO"
>
> I rebooted again, but for some reason I still get the same error for
> "su."
>
> So basically, I locked myself out of my box completely. I fail :-(
>
> su has the following permissions:
> -r-s
ot;NO"
>
> I rebooted again, but for some reason I still get the same error for
> "su."
>
> So basically, I locked myself out of my box completely. I fail :-(
>
> su has the following permissions:
> -r-sr-xr-x 1 root wheel schg 12240 May 13 13:15 su
>
I can't become root, so I pulled the plug and
rebooted into single-user mode. I edited /etc/rc.conf and set
kern_securelevel_enable="NO"
I rebooted again, but for some reason I still get the same error for "su."
So basically, I locked myself out of my box completely. I
22 matches
Mail list logo
