From owner-freebsd-questions@FreeBSD.ORG Thu May 20 16:48:00 2010 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 06E9E1065678 for ; Thu, 20 May 2010 16:48:00 +0000 (UTC) (envelope-from vogelke@hcst.com) Received: from beta.hcst.com (beta.hcst.com [192.52.183.241]) by mx1.freebsd.org (Postfix) with ESMTP id ACC378FC16 for ; Thu, 20 May 2010 16:47:59 +0000 (UTC) Received: from beta.hcst.com (localhost [127.0.0.1]) by beta.hcst.com (8.13.8/8.13.8/Debian-3) with ESMTP id o4KGlwvT024999 for ; Thu, 20 May 2010 12:47:58 -0400 Received: (from vogelke@localhost) by beta.hcst.com (8.13.8/8.13.8/Submit) id o4KGlwRq024998; Thu, 20 May 2010 12:47:58 -0400 Received: by bsd118.wpafb.af.mil (Postfix, from userid 583) id 0348ABE71; Wed, 19 May 2010 21:35:03 -0400 (EDT) To: freebsd-questions@freebsd.org In-reply-to: <877hmzbi1f.fsf@cjlinux.localnet> (message from Carl Johnson on Wed, 19 May 2010 16:14:52 -0700) Organization: Array Infotech X-Disclaimer: I don't speak for the USAF or Array Infotech. X-GPG-ID: 1024D/711752A0 2006-06-27 Karl Vogel X-GPG-Fingerprint: 56EB 6DBF 4224 C953 F417 CC99 4C7C 7D46 7117 52A0 References: <877hmzbi1f.fsf@cjlinux.localnet> Message-Id: <20100520013503.0348ABE71@bsd118.wpafb.af.mil> Date: Wed, 19 May 2010 21:35:03 -0400 (EDT) From: vogelke+unix@pobox.com (Karl Vogel) Subject: Re: Bash lockups X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 20 May 2010 16:48:00 -0000 >> On Wed, 19 May 2010 16:14:52 -0700, >> Carl Johnson said: C> I have been experimenting with FreeBSD for a while, and I consistently C> get bash lockups at irregular intervals when it is otherwise idle. C> Does anybody have any suggestings on how I could try to trace this? 1. Get a process-table list every minute or so via cron. It might show something else running or trying to run when you have your lockups. Try "ps -axw -o user,pid,ppid,pgid,tt,start,time,command". 2. Get the PID of the bash session, and run something like this as root: pid=12345 k=1 while true; do truss -p $pid 2>&1 | head -1000 > /dir-with-lots-of-space/$k k=`expr $k + 1` done This should break the truss output into 1000-line chunks and let you clean out the directory before it chews up all your space. Hopefully one of the truss files will show something useful after a lockup. -- Karl Vogel I don't speak for the USAF or my company REMOTE CONTROL - female, because it gives a man pleasure, he'd be lost without it, and while he doesn't always know the right buttons to push, he keeps trying. --from the "What gender are they?" list