Skip site navigation (1)Skip section navigation (2)
Date:      Fri, 8 Aug 2008 12:20:58 -0500
From:      Matt <datahead4@gmail.com>
To:        ports@freebsd.org
Subject:   Re: FreeBSD Port: fusefs-libs-2.7.2_1 - gvfs-fuse-daemon process(es) stuck
Message-ID:  <cd6b4a5b0808081020y709a07d7t642798ce40ba8cce@mail.gmail.com>
In-Reply-To: <20080507153339.GA61304@eos.sc1.parodius.com>
References:  <cd6b4a5b0805052220i87f274fnd5f08618d9a72fef@mail.gmail.com> <20080506053244.GA94936@eos.sc1.parodius.com> <cd6b4a5b0805070719h63a7c507s6e5545b1af4a31c3@mail.gmail.com> <20080507143004.GA59170@eos.sc1.parodius.com> <1210171696.30323.2.camel@squirrel.corp.cox.com> <cd6b4a5b0805070753k4daa6b14mceb4802fd1cb7f8c@mail.gmail.com> <cd6b4a5b0805070822y56e9072ag5b3e33fd2d669600@mail.gmail.com> <20080507153339.GA61304@eos.sc1.parodius.com>

next in thread | previous in thread | raw e-mail | index | archive | help
On Wed, May 7, 2008 at 10:33 AM, Jeremy Chadwick <koitsu@freebsd.org> wrote:
>
> On Wed, May 07, 2008 at 10:22:09AM -0500, Matt wrote:
>  > On Wed, May 7, 2008 at 9:53 AM, Matt <datahead4@gmail.com> wrote:
>  > > On Wed, May 7, 2008 at 9:48 AM, Robert Noland <rnoland@2hip.net> 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.
>
As a (very) late follow-up to this issue, looks like the latest Gnome
ports have eliminated this issue.  I haven't seen it for the last few
weeks after doing a full portupgrade on Gnome.

Thanks,
Matt



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?cd6b4a5b0808081020y709a07d7t642798ce40ba8cce>