Date: Tue, 16 Jun 2009 20:52:54 -0700 (PDT) From: Unga <unga888@yahoo.com> To: Tim Judd <tajudd@gmail.com> Cc: freebsd-questions@freebsd.org Subject: Re: Cannot login as root, exited on signal 11 Message-ID: <958562.35592.qm@web57008.mail.re3.yahoo.com>
next in thread | raw e-mail | index | archive | help
--- On Wed, 6/17/09, Tim Judd <tajudd@gmail.com> wrote:=0A=0A> From: Tim Ju= dd <tajudd@gmail.com>=0A> Subject: Re: Cannot login as root, exited on sign= al 11=0A> To: "Unga" <unga888@yahoo.com>=0A> Cc: freebsd-questions@freebsd.= org=0A> Date: Wednesday, June 17, 2009, 2:51 AM=0A> On 6/16/09, Unga <unga8= 88@yahoo.com>=0A> wrote:=0A> >=0A> > --- On Tue, 6/16/09, Tim Judd <tajudd@= gmail.com>=0A> wrote:=0A> >=0A> >> From: Tim Judd <tajudd@gmail.com>=0A> >>= Subject: Re: Cannot login as root, exited on=0A> signal 11=0A> >> To: "Ung= a" <unga888@yahoo.com>=0A> >> Cc: freebsd-questions@freebsd.org,=0A> mail25= @bzerk.org=0A> >> Date: Tuesday, June 16, 2009, 10:10 PM=0A> >> su -l disca= rds the previous=0A> >> environment and loads a new environment.=0A> >> It'= s as if you're "logging in" as root (-l)=0A> >>=0A> >> running su without -= l will elevate your=0A> priveledges without=0A> >> this same=0A> >> problem= , you keep the same shell.=A0 Fix your=0A> shell=0A> >> problems via this= =0A> >> way (or single user as originally described), and=0A> be=0A> >> car= eful next=0A> >> time.=0A> >>=0A> >=0A> > Hi Tim, thanks for the reply. I h= ave not identified=0A> yet the problem to be=0A> > solved.=0A> >=0A> > If y= ou refer that I use bash for root is the problem,=0A> there is no differenc= e=0A> > by switching root's shell to sh.=0A> >=0A> > With sh as the shell f= or root:=0A> > 1. Still cannot login as root from the console. Child=0A> pr= ocess died error.=0A> >=0A> > 2. "su -l" doesn't work, child process died e= rror.=0A> >=0A> > 3. su works. But the prompt is [\u@host name]#=0A> > Why = it doesn't print root@host? whoami shows root.=0A> >=0A> > What is the prob= lem you think that I should fix? any=0A> ideas? any thread=0A> > related er= ror as the child process die when in root?=0A> >=0A> > Best regards=0A> > U= nga=0A> >=0A> =0A> =0A> Unga,=0A> =0A> This is the first time I've read fro= m you that you were=0A> using the=0A> recommended shell.=A0 Given you're ru= nning the=0A> recommended shell and=0A> you're still having problems sporad= ically (users =3D ok, root=0A> =3D not),=0A> I'd start the invasive discove= ry why it's not=0A> working.=A0 First is=0A> system-wide:=0A> =A0 is your k= ernel version and userland in sync?=0A> =0A> =A0 Such as RELENG_7 userland = with RELENG_7=0A> kernel?=A0 Running=0A> non-synchronized kernel and userla= nd (aka world) is not=0A> supported* and=0A> will cause problems.=0A> =0A> = =0A> Back to the individualized problem -- if you backup your=0A> root's=0A= > dotfiles, and then remove or rename them, does the problem=0A> remain?=0A= > What if you set root's home directory to one of your user's=0A> home=0A> = directory as a test to see if it's the dotfiles?=0A> =0A> =0A> These would = be my next steps to diagnose what might be the=0A> problem.=A0 Good luck.= =0A> =0A> =0A> * - Only supported is when you're upgrading and have a=0A> n= ewer kernel=0A> just long enough to install world.=0A> =0A=0ADear Tim=0A=0A= I suspect this is a build error. Therefore, let me rebuild and see whether = the problem go away. I'm going to do a careful rebuild more towards the end= of the week. I'll let the list and you know the result. If the problem sti= ll persists, I really like to know what causes it.=0A=0ABest regards=0AUnga= =0A=0A=0A
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?958562.35592.qm>