From owner-freebsd-ports@FreeBSD.ORG Wed May 7 14:53:29 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 130121065670 for ; Wed, 7 May 2008 14:53:29 +0000 (UTC) (envelope-from datahead4@gmail.com) Received: from yw-out-2324.google.com (yw-out-2324.google.com [74.125.46.29]) by mx1.freebsd.org (Postfix) with ESMTP id BBC178FC0A for ; Wed, 7 May 2008 14:53:28 +0000 (UTC) (envelope-from datahead4@gmail.com) Received: by yw-out-2324.google.com with SMTP id 9so194751ywe.13 for ; Wed, 07 May 2008 07:53:22 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; bh=HYegVq+cEwGXl/2zPRLN+hNwe3v71CPxpFra/Mx8Sfw=; b=ZyNJ/fjzHiqHH1JJ1bhI+jsVdEHw+JsCGfm63KT7B1oNz25nwHjTe0hULBtIyYEooeVxvISTm4EKD1L3zUxt9UwsKYpuAxx5z+VrQr2i0t3loHkjN9ZMoM6oTW0PcRNziEGp54x2S7+xZev/s2GYUkXVPJU3U/ZJAhEBE4HfYeA= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=HTK7bsIL5gXcRhNw9qjjLJphe0vuMbfSse5nKJ6rwUmptpnn0Tc2FCZS5OMDsNFc5GPhg+HpB5Turf0kt6/OzdLJd259uTkhAJZeu1UuSsszEfT54MAM7XSDjugRIpKB2zA/Da95xvccIQooemD/evjoeUy8voyOdaSXLfuBH5A= Received: by 10.142.99.21 with SMTP id w21mr913470wfb.108.1210172001432; Wed, 07 May 2008 07:53:21 -0700 (PDT) Received: by 10.143.122.6 with HTTP; Wed, 7 May 2008 07:53:21 -0700 (PDT) Message-ID: Date: Wed, 7 May 2008 09:53:21 -0500 From: Matt To: "Robert Noland" In-Reply-To: <1210171696.30323.2.camel@squirrel.corp.cox.com> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <20080506053244.GA94936@eos.sc1.parodius.com> <20080507143004.GA59170@eos.sc1.parodius.com> <1210171696.30323.2.camel@squirrel.corp.cox.com> Cc: ports@freebsd.org, Jeremy Chadwick , 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:53:29 -0000 On Wed, May 7, 2008 at 9:48 AM, Robert Noland wrote: > On Wed, 2008-05-07 at 07:30 -0700, Jeremy Chadwick wrote: > > 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. > > I don't want to state the obvious, but attaching to the process with gdb > will produce the stopped state. Was this ps snap taken before or after > attaching with gdb? > My fault - bad order of info gathering. Here's a ps snap after sending the process -CONT signal: [mtosto@mtosto-bsd ~]$ ps -axlH | grep vfs 1000 4019 1 0 46 0 6324 2412 uwait Ts ?? 0:00.00 /usr/local/libexec//gvfs-fuse-daemon /home/mtosto/.gvfs 1000 4019 1 0 44 0 6324 2412 - Ts ?? 0:00.00 /usr/local/libexec//gvfs-fuse-daemon /home/mtosto/.gvfs > robert. > > > > > 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). > > > >