From owner-freebsd-questions@FreeBSD.ORG Fri May 21 00:26:32 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 B8E371065673 for ; Fri, 21 May 2010 00:26:32 +0000 (UTC) (envelope-from carlj@peak.org) Received: from redcondor1.peak.org (redcondor1.peak.org [69.59.192.54]) by mx1.freebsd.org (Postfix) with ESMTP id 801F68FC0C for ; Fri, 21 May 2010 00:26:32 +0000 (UTC) Received: from peak-mail-gateway.peak.org ([69.59.192.42]) by redcondor1.peak.org ({e03e86cd-14ae-47ce-9578-3c080ce9c462}) via TCP (outbound) with ESMTP id 20100521002631631 for ; Fri, 21 May 2010 00:26:31 +0000 X-RC-FROM: X-RC-RCPT: Received: from cjlinux.localnet (207.55.91.197.peak.org [207.55.91.197] (may be forged)) (authenticated bits=0) by peak-mail-gateway.peak.org (8.12.10/8.12.8) with ESMTP id o4L0QUu4073823 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=NO) for ; Thu, 20 May 2010 17:26:31 -0700 (PDT) Received: from carlj by cjlinux.localnet with local (Exim 4.69) (envelope-from ) id 1OFG4L-0003vW-N3 for freebsd-questions@freebsd.org; Thu, 20 May 2010 17:26:29 -0700 To: freebsd-questions@freebsd.org References: <877hmzbi1f.fsf@cjlinux.localnet> <20100520013503.0348ABE71@bsd118.wpafb.af.mil> From: Carl Johnson Date: Thu, 20 May 2010 17:26:29 -0700 In-Reply-To: <20100520013503.0348ABE71@bsd118.wpafb.af.mil> (Karl Vogel's message of "Wed\, 19 May 2010 21\:35\:03 -0400 \(EDT\)") Message-ID: <8739xmt80a.fsf@cjlinux.localnet> User-Agent: Gnus/5.11 (Gnus v5.11) Emacs/22.2 (gnu/linux) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii 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: Fri, 21 May 2010 00:26:32 -0000 vogelke+unix@pobox.com (Karl Vogel) writes: >>> 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. Thanks for the ideas. I keep several windows with shells open so I don't want to trace all of them yet. I don't even know what the shells are doing when they lock up, so for now I'll just wait until one locks up and then try truss to see what it is actually doing. This happens only occasionally, so I will probably have to wait a while. I don't know this is actually just a bash problem since I have never had it happen running on Linux in at least 10 years. -- Carl Johnson carlj@peak.org