Re: FreeBSD Port: fusefs-libs-2.7.2_1 - gvfs-fuse-daemon process(es) stuck

2008-08-08 Thread Matt
On Wed, May 7, 2008 at 10:33 AM, Jeremy Chadwick <[EMAIL PROTECTED]> wrote: > > On Wed, May 07, 2008 at 10:22:09AM -0500, Matt wrote: > > On Wed, May 7, 2008 at 9:53 AM, Matt <[EMAIL PROTECTED]> wrote: > > > On Wed, May 7, 2008 at 9:48 AM, Robert Noland <[EMAIL PROTECTED]> wrote: > > > > On Wed

Re: FreeBSD Port: fusefs-libs-2.7.2_1 - gvfs-fuse-daemon process(es) stuck

2008-05-07 Thread Jeremy Chadwick
On Wed, May 07, 2008 at 10:22:09AM -0500, Matt wrote: > On Wed, May 7, 2008 at 9:53 AM, Matt <[EMAIL PROTECTED]> wrote: > > On Wed, May 7, 2008 at 9:48 AM, Robert Noland <[EMAIL PROTECTED]> wrote: > > > On Wed, 2008-05-07 at 07:30 -0700, Jeremy Chadwick wrote: > > > > On Wed, May 07, 2008 at 09:

Re: FreeBSD Port: fusefs-libs-2.7.2_1 - gvfs-fuse-daemon process(es) stuck

2008-05-07 Thread Robert Noland
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 s

Re: FreeBSD Port: fusefs-libs-2.7.2_1 - gvfs-fuse-daemon process(es) stuck

2008-05-07 Thread Matt
On Wed, May 7, 2008 at 9:53 AM, Matt <[EMAIL PROTECTED]> wrote: > On Wed, May 7, 2008 at 9:48 AM, Robert Noland <[EMAIL PROTECTED]> 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

Re: FreeBSD Port: fusefs-libs-2.7.2_1 - gvfs-fuse-daemon process(es) stuck

2008-05-07 Thread Matt
On Wed, May 7, 2008 at 9:48 AM, Robert Noland <[EMAIL PROTECTED]> 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 p

Re: FreeBSD Port: fusefs-libs-2.7.2_1 - gvfs-fuse-daemon process(es) stuck

2008-05-07 Thread Jeremy Chadwick
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

Re: FreeBSD Port: fusefs-libs-2.7.2_1 - gvfs-fuse-daemon process(es) stuck

2008-05-07 Thread Matt
On Tue, May 6, 2008 at 12:32 AM, Jeremy Chadwick <[EMAIL PROTECTED]> wrote: > On Tue, May 06, 2008 at 12:20:17AM -0500, Matt wrote: > > The symptom is as described above - the gvfs-fuse-daemon processes do > > not exit cleanly and more processes continue to build-up whenever I > > complete an X-

Re: FreeBSD Port: fusefs-libs-2.7.2_1 - gvfs-fuse-daemon process(es) stuck

2008-05-05 Thread Jeremy Chadwick
On Tue, May 06, 2008 at 12:20:17AM -0500, Matt wrote: > The symptom is as described above - the gvfs-fuse-daemon processes do > not exit cleanly and more processes continue to build-up whenever I > complete an X-session. The processes do exit when I send them a > manual kill signal. The only info

FreeBSD Port: fusefs-libs-2.7.2_1 - gvfs-fuse-daemon process(es) stuck

2008-05-05 Thread Matt
Hello. I am seeing gvfs-fuse-daemon processes remain stuck in memory after logging out of the system, and it appears that it may have something to do with the fuse libraries. I asked about this on the FreeBSD GNOME mailing list and it was suggested that I get the information to the fusefs-libs ma