From owner-freebsd-hackers@FreeBSD.ORG Tue Jan 20 08:19:18 2004 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 76CAF16A4CE for ; Tue, 20 Jan 2004 08:19:18 -0800 (PST) Received: from lakemtao03.cox.net (lakemtao03.cox.net [68.1.17.242]) by mx1.FreeBSD.org (Postfix) with ESMTP id 333F743D46 for ; Tue, 20 Jan 2004 08:19:14 -0800 (PST) (envelope-from brian@shadowcom.net) Received: from shadowcom.net ([68.100.212.237]) by lakemtao03.cox.net (InterMail vM.5.01.06.05 201-253-122-130-105-20030824) with SMTP id <20040120161914.NCPZ2192.lakemtao03.cox.net@shadowcom.net> for ; Tue, 20 Jan 2004 11:19:14 -0500 Received: (qmail 1968 invoked by uid 500); 20 Jan 2004 16:19:13 -0000 Date: Tue, 20 Jan 2004 11:19:13 -0500 From: Brian Ledbetter To: freebsd-hackers@freebsd.org Message-ID: <20040120161913.GB1289@shadowcom.net> References: <20040120160843.GA1289@shadowcom.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20040120160843.GA1289@shadowcom.net> User-Agent: Mutt/1.4i Subject: Re: Curious problem w/ 5.2-RELEASE su X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 20 Jan 2004 16:19:18 -0000 Additionally, I am seeing this message in syslog: Jan 20 10:48:26 tokyo su: in openpam_load_module(): no pam_wheel.so found though /usr/lib/pam_wheel.so -> /usr/lib/pam_wheel.so.2 exists, and has the same md5 hash as on the working host. What am I missing here? On Tue, Jan 20, 2004 at 11:08:43AM -0500, Brian Ledbetter wrote: > I have two systems which I recently upgraded from src to > 5.2-RELEASE. (Both systems were upgraded from the same > /usr/src tree) Everything seemed to be working fine until > a little while ago this morning, when I started having this > problem with /usr/bin/su: > > $ su - > su in free(): error: chunk is already free > Abort trap (core dumped) > $ sudo sh > $ id > uid=0(root) gid=0(wheel) groups=0(wheel), 2(kmem), 3(sys), > 4(tty), 5(operator), 20(staff), 31(guest) > $ su - > su in free(): error: chunk is already free > Abort trap (core dumped) > > Does anyone have any idea what would be causing this? The > MD5 hash of /usr/bin/su and all linked libraries are identical > between the two systems, but /usr/sbin/su works just fine on > the other host. dmesg reports nothing unusual on system startup. > What can I do to fix this? > > Thanks in advance! > > -- > Brian C. Ledbetter > http://www.shadowcom.net/brian/ > _______________________________________________ > freebsd-hackers@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-hackers > To unsubscribe, send any mail to "freebsd-hackers-unsubscribe@freebsd.org" -- Brian C. Ledbetter http://www.shadowcom.net/brian/