From owner-freebsd-ports@FreeBSD.ORG Wed May 7 14:30:05 2008 Return-Path: Delivered-To: ports@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 642A6106564A for ; Wed, 7 May 2008 14:30:05 +0000 (UTC) (envelope-from jdc@parodius.com) Received: from mx01.sc1.parodius.com (mx01.sc1.parodius.com [72.20.106.3]) by mx1.freebsd.org (Postfix) with ESMTP id 5075B8FC16 for ; Wed, 7 May 2008 14:30:05 +0000 (UTC) (envelope-from jdc@parodius.com) Received: by mx01.sc1.parodius.com (Postfix, from userid 1000) id E88481CC05B; Wed, 7 May 2008 07:30:04 -0700 (PDT) Date: Wed, 7 May 2008 07:30:04 -0700 From: Jeremy Chadwick To: Matt Message-ID: <20080507143004.GA59170@eos.sc1.parodius.com> References: <20080506053244.GA94936@eos.sc1.parodius.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.17 (2007-11-01) Cc: ports@freebsd.org, amistry@am-productions.biz Subject: Re: FreeBSD Port: fusefs-libs-2.7.2_1 - gvfs-fuse-daemon process(es) stuck X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 07 May 2008 14:30:05 -0000 On Wed, May 07, 2008 at 09:19:24AM -0500, Matt wrote: > Sorry - should have been more specific than the generic "stuck" > description. Top shows the process state as "fu_msg" and it is not > consuming any processor resources, just seemingly sits there idling. > Output from ps is: > > UID PID PPID CPU PRI NI VSZ RSS MWCHAN STAT TT TIME COMMAND > 1000 4019 1 0 44 0 6324 2528 - Ts ?? 0:00.00 > /usr/local/libexec//gvfs-fuse-daemon /home/mtosto The "T" flag under State says that the process is stopped. It's as if the process was running in the foreground, and was ^Z'd -- same behaviour. The part which confuses me (I'm sure others can explain this part) is that the parent PID is 1, which is init. This would indicate that the process is actually a zombie whose parent has been killed off, and the child's parent has been assigned to init. You might try doing a "kill -CONT" on the process to see what happens. I don't think truss or ktrace are going to help here, because something is explicitly stopping the process (SIGSTOP or some other means). -- | Jeremy Chadwick jdc at parodius.com | | Parodius Networking http://www.parodius.com/ | | UNIX Systems Administrator Mountain View, CA, USA | | Making life hard for others since 1977. PGP: 4BD6C0CB |