Date: Thu, 20 May 2010 17:26:29 -0700 From: Carl Johnson <carlj@peak.org> To: freebsd-questions@freebsd.org Subject: Re: Bash lockups Message-ID: <8739xmt80a.fsf@cjlinux.localnet> In-Reply-To: <20100520013503.0348ABE71@bsd118.wpafb.af.mil> (Karl Vogel's message of "Wed\, 19 May 2010 21\:35\:03 -0400 \(EDT\)") References: <877hmzbi1f.fsf@cjlinux.localnet> <20100520013503.0348ABE71@bsd118.wpafb.af.mil>
next in thread | previous in thread | raw e-mail | index | archive | help
vogelke+unix@pobox.com (Karl Vogel) writes: >>> On Wed, 19 May 2010 16:14:52 -0700, >>> Carl Johnson <carlj@peak.org> 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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?8739xmt80a.fsf>