Skip site navigation (1)Skip section navigation (2)
Date:      Fri, 03 Jul 2009 07:51:47 -0500
From:      "Sagara Wijetunga" <sagara@tomahawk.com.sg>
To:        Roland Smith <rsmith@xs4all.nl>
Cc:        freebsd-stable@freebsd.org
Subject:   Re: FreeBSD child process die for root
Message-ID:  <20090703125147.6649.qmail@us1.tomahawkonline.net>
In-Reply-To: <20090702175722.GA75808@slackbox.xs4all.nl>
References:  <20090701070409.7740.qmail@us1.tomahawkonline.net> <20090701174930.GC37269@slackbox.xs4all.nl> <20090702012352.17934.qmail@us1.tomahawkonline.net> <20090702062738.GA58158@slackbox.xs4all.nl> <20090702041707.19651.qmail@us1.tomahawkonline.net> <20090702175722.GA75808@slackbox.xs4all.nl>

next in thread | previous in thread | raw e-mail | index | archive | help
Roland Smith writes:=20

>=20
> Is there anything else from su in the logfiles? That might help narrow =
down
> where it crashes.=20
>
No, other than the same =E2=80=9Cuid 0: exited on signal 11=E2=80=9D for =
login, su and=20
cron. What we see is after the fork, child process run for some time and=20
crashes.=20


> Are you using the standard FreeBSD su? If not, check your
> modifications. Does the version of the userland that you are using matc=
h
> the version of the kernel?=20
>=20
Our su is slightly modified. Tomorrow, I can try with standard su. Our=20
userland is in some areas different. We normally try to use newer version=
s=20
wherever possible. Our build method used to produce acceptable systems ti=
ll=20
FreeBSD 7.0. Its only on FreeBSD 7.2 now this issue. Other than that ther=
e=20
is no other noticeable issue.=20


> I've verified that 'su -l' works fine on FreeBSD 7.2-RELEASE-p2 on the
> amd64 architecture. =20
>=20
> What you could do is run 'su -l' under a debugger. =20
>=20

I just ran our normal su (without debugging info) under gdb:
gdb /usr/bin/su
GNU gdb 6.6
This GDB was configured as "i386-unknown-freebsd7.2"...
(no debugging symbols found)
(gdb) run -l
Starting program: /usr/bin/su -l
(no debugging symbols found)
(no debugging symbols found)
su: not running setuid=20

Program exited with code 01.=20


ls -l /usr/bin/su
 -r-sr-xr-x  1 root  freebsd  14452 Jun 28 13:50 /usr/bin/su=20

This shows su is setuid root.=20

Anyway, I'll run su with debugging info tomorrow.=20

regards
Sagara



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20090703125147.6649.qmail>