From owner-freebsd-questions@FreeBSD.ORG Thu Feb 17 01:32:09 2005 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 2044716A4CF; Thu, 17 Feb 2005 01:32:09 +0000 (GMT) Received: from neutrino.merly.org (neutrino.merly.org [64.81.246.50]) by mx1.FreeBSD.org (Postfix) with ESMTP id C181A43D41; Thu, 17 Feb 2005 01:32:08 +0000 (GMT) (envelope-from tonytung@merly.org) Received: from neutrino.merly.org (localhost [127.0.0.1]) by neutrino.merly.org (8.13.1/8.13.1) with ESMTP id j1H1W89M039093 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 16 Feb 2005 17:32:08 -0800 (PST) (envelope-from tonytung@merly.org) Received: from localhost (tonytung@localhost)j1H1W71Q039090; Wed, 16 Feb 2005 17:32:07 -0800 (PST) (envelope-from tonytung@merly.org) X-Authentication-Warning: neutrino.merly.org: tonytung owned process doing -bs Date: Wed, 16 Feb 2005 17:32:07 -0800 (PST) From: Tony Tung To: "Greg 'groggy' Lehey" In-Reply-To: <20050217012601.GI69640@wantadilla.lemis.com> Message-ID: References: <20050217012601.GI69640@wantadilla.lemis.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed cc: freebsd-questions@FreeBSD.org Subject: Re: emacs on freebsd 5.3 X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 17 Feb 2005 01:32:10 -0000 On Thu, 17 Feb 2005, Greg 'groggy' Lehey wrote: > On Wednesday, 16 February 2005 at 17:20:24 -0800, Tony Tung wrote: >> >> Hi, >> >> I have an unusual problem I was hoping someone could help me with. I have >> a FreeBSD 5.3 server that's been up for longer than a month. In that >> period, everything seemed fine. However, all of a sudden, I'm no longer >> able to spawn a shell in emacs. In fact, I cannot start any process >> (shell, gdb, grep, compile) inside emacs. It is happening to all the >> users, which makes me wonder if there's some OS-related issue in play >> here. >> >> I've tried restarting emacs, bypassing the emacs startup file, >> reinstalling emacs, and just about everything I could think of short of >> restarting the server (don't want to do that until I'm physically >> present). > > It would be worth attaching a ktrace to the Emacs to see what it's > doing. Something like this: > > $ ps aux | grep emacs > root 12978 0.0 1.3 12880 9832 p5 R 8Oct04 222:09.31 emacs > $ ktrace -i -p 12978 > (in Emacs, do your thing) > $ ktrace -C -p 12978 > $ kdump | less > > You should then look for a call to fork or execve and see what errors > are returned. > > Greg Hi, Strangely enough, that seems to have fixed the problem. Other users are seeing a return to "normal" behavior as well. Thanks, Tony