Date: Wed, 1 Jul 2009 19:49:31 +0200 From: Roland Smith <rsmith@xs4all.nl> To: Sagara Wijetunga <sagara@tomahawk.com.sg> Cc: freebsd-stable@freebsd.org Subject: Re: FreeBSD child process die for root Message-ID: <20090701174930.GC37269@slackbox.xs4all.nl> In-Reply-To: <20090701070409.7740.qmail@us1.tomahawkonline.net> References: <20090701070409.7740.qmail@us1.tomahawkonline.net>
next in thread | previous in thread | raw e-mail | index | archive | help
[-- Attachment #1 --] On Wed, Jul 01, 2009 at 02:04:09AM -0500, Sagara Wijetunga wrote: > Hi > > I'm Sagara Wijetunga from Tomahawk Computers from Singapore, makers of the > Tomahawk Desktop, a FreeBSD based desktop operating system > (http://www.tomahawkcomputers.com/) which is free for personal use. > > Ever since we upgraded our Tomahawk Core OS to the FreeBSD 7.2 sources, we > experienced a strange issue as follows: > > 1. The root cannot login from the console, child process forked die with > “uid 0: exited on signal 11”. > 2. Normal users can log in, no issue. > 3. Normal users can type “su” and become root, but “su -l” > results child process forked die with “uid 0: exited on signal 11”. > 4. The /var/log/messages shows “(cron), uid 0: exited on signal 11 > (core dumped)” Based on your symptoms, it looks like something in the restart commands file for root causes the shell to crash... What shell are you using for root? Roland -- R.F.Smith http://www.xs4all.nl/~rsmith/ [plain text _non-HTML_ PGP/GnuPG encrypted/signed email much appreciated] pgp: 1A2B 477F 9970 BA3C 2914 B7CE 1277 EFB0 C321 A725 (KeyID: C321A725) [-- Attachment #2 --] -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.12 (FreeBSD) iEYEARECAAYFAkpLoaoACgkQEnfvsMMhpyU8FwCfbRXwGQVvB8oLvHlE8qjxNfLg JTYAmwYYtdwQBrvnHsjeORiG0XaycbVG =onz1 -----END PGP SIGNATURE-----
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20090701174930.GC37269>