Cannot login as root, exited on signal 11
tajudd at gmail.com
Tue Jun 16 14:10:57 UTC 2009
su -l discards the previous environment and loads a new environment.
It's as if you're "logging in" as root (-l)
running su without -l will elevate your priveledges without this same
problem, you keep the same shell. Fix your shell problems via this
way (or single user as originally described), and be careful next
On 6/16/09, Unga <unga888 at yahoo.com> wrote:
> --- On Tue, 6/16/09, Ruben de Groot <mail25 at bzerk.org> wrote:
>> From: Ruben de Groot <mail25 at bzerk.org>
>> Subject: Re: Cannot login as root, exited on signal 11
>> To: "Glen Barber" <glen.j.barber at gmail.com>
>> Cc: "Unga" <unga888 at yahoo.com>, freebsd-questions at freebsd.org
>> Date: Tuesday, June 16, 2009, 4:06 PM
>> On Mon, Jun 15, 2009 at 02:37:54PM
>> -0400, Glen Barber typed:
>> > On Mon, Jun 15, 2009 at 9:27 AM, Ruben de Groot<mail25 at bzerk.org>
>> > >> If so, reboot into single-user mode, and
>> change it back.
>> > >
>> > > Why reboot? You can "su -s /bin/tcsh"
>> > >
>> > How can you change the shell if you cannot log
>> in? That's why I
>> > suggested single-user mode.
>> He said he could log in as a normal user.
> Yes, normal users can log in. Its only root cannot.
> Normal user, after log in, can su to root but "su -l" develops the same
> problem, the child process die.
> All users use bash shell.
> What is "su -l" requires that su doesn't?
> Best regards
> freebsd-questions at freebsd.org mailing list
> To unsubscribe, send any mail to "freebsd-questions-unsubscribe at freebsd.org"
More information about the freebsd-questions