From owner-freebsd-gnome@FreeBSD.ORG Sun Feb 7 20:25:27 2010 Return-Path: Delivered-To: freebsd-gnome@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 9FE7C1065672 for ; Sun, 7 Feb 2010 20:25:27 +0000 (UTC) (envelope-from gperez@entel.upc.edu) Received: from violet.upc.es (violet.upc.es [147.83.2.51]) by mx1.freebsd.org (Postfix) with ESMTP id 27DB98FC13 for ; Sun, 7 Feb 2010 20:25:26 +0000 (UTC) Received: from ackerman2.upc.es (ackerman2.upc.es [147.83.2.244]) by violet.upc.es (8.14.1/8.13.1) with ESMTP id o17KPPW0018805 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL); Sun, 7 Feb 2010 21:25:25 +0100 Received: from [192.168.100.200] (9.Red-88-11-97.dynamicIP.rima-tde.net [88.11.97.9]) (authenticated bits=0) by ackerman2.upc.es (8.13.8/8.13.8) with ESMTP id o17KPN9g013246 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Sun, 7 Feb 2010 21:25:24 +0100 Message-ID: <4B6F21B3.1020303@entel.upc.edu> Date: Sun, 07 Feb 2010 21:25:23 +0100 From: =?ISO-8859-1?Q?Gustau_P=E9rez?= User-Agent: Thunderbird 2.0.0.23 (X11/20100207) MIME-Version: 1.0 To: freebsd-gnome@freebsd.org References: <4B6D4624.803@entel.upc.edu> <4B6F1D6B.2070408@entel.upc.edu> <1265573861.24140.3.camel@shumai.marcuscom.com> In-Reply-To: <1265573861.24140.3.camel@shumai.marcuscom.com> X-Enigmail-Version: 0.95.7 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-Scanned-By: MIMEDefang 2.63 on 147.83.2.244 X-Mail-Scanned: Criba 2.0 + Clamd X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-3.0 (violet.upc.es [147.83.2.51]); Sun, 07 Feb 2010 21:25:25 +0100 (CET) Cc: Subject: Re: Problems accessing files with gvfs-fuse-daemon X-BeenThere: freebsd-gnome@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: GNOME for FreeBSD -- porting and maintaining List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 07 Feb 2010 20:25:27 -0000 >>> I posted the trace to pastebin : >>> >>> http://pastebin.com/m79cf37f3 >>> >>> If you search for socket syscalls, you'll see it normally creates two, >>> and then it connects them to a unix socket in /var/tmp. For example I >>> see it connecting two sockets to >>> >>> /var/tmp/gvfs-gus-B9lo36Ky/socket1 >>> /var/tmp/gvfs-gus-B9lo36Ky/socket2 >>> >>> But only the second can be found. I can't see the first. So probably >>> this is the problem. Anyone has the same problem ? I can provide more info. >>> > > As I said, you would be better off contacting the fuse maintainer. > > Joe > > Hi again, Well, I think those files had been openened by gvfs-fuse-daemon, I see gvfs-fuse-daemon opening them in the trace file. So I'm not sure whether it is fuse responsability or not. Am I right ? If you still think it is fuse responsability I'll contact the fuse mantainer, but it is kinda strange fusefs-ssh has not that problem in my config. Do you guys have the same problem accessing $HOME/.gvfs files ? Thanks Joe, Gus -- PGP KEY : http://www-entel.upc.edu/gus/gus.asc