From owner-freebsd-gnome Mon Feb 24 21:25: 5 2003 Delivered-To: freebsd-gnome@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 7035337B401 for ; Mon, 24 Feb 2003 21:25:04 -0800 (PST) Received: from hotmail.com (f89.pav1.hotmail.com [64.4.31.89]) by mx1.FreeBSD.org (Postfix) with ESMTP id 135D043F75 for ; Mon, 24 Feb 2003 21:25:04 -0800 (PST) (envelope-from verbophobe@hotmail.com) Received: from mail pickup service by hotmail.com with Microsoft SMTPSVC; Mon, 24 Feb 2003 21:25:03 -0800 Received: from 24.202.170.180 by pv1fd.pav1.hotmail.msn.com with HTTP; Tue, 25 Feb 2003 05:25:03 GMT X-Originating-IP: [24.202.170.180] From: "Maxime Romano" To: gnome@freebsd.org Subject: Gconf and NFS homedirs Date: Tue, 25 Feb 2003 05:25:03 +0000 Mime-Version: 1.0 Content-Type: text/plain; format=flowed Message-ID: X-OriginalArrivalTime: 25 Feb 2003 05:25:03.0979 (UTC) FILETIME=[402A83B0:01C2DC8E] Sender: owner-freebsd-gnome@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Morning, Upon startup of a gnome session, gconf complains that it can't lock the file ~/.gconf/%gconf-xml-backend.lock/ior . So, making sure that gconf isn't running, I delete that nasty file, and restart gnome. It seems to really want to start, but then it outputs hundreds of messages to /var/log/messages explaining that it can't lock ~/.gconfd/lock/ior, and the whole session goes haywire. Once that file is deleted, gconf will start without complaining, and the session will continue as normal. I've looked around, and according to http://www.gnome.org/projects/gconf/ (Look under the "I'm having a lock file problem. What do I do?" heading), it's caused by my NFS mounted home directory, and that fact that rpc.statd and rpc.lockd aren't running on both machines. Now, I first (gasp!) had this problem when I upgraded the client machine to 5.0-rel. At that time, the rpc processes weren't started on either machines. I stuck rpc_statd_enable="YES" and rpc_lockd_enable="YES" in rc.conf on both machines and everything went back to normal. Yesterday, however, I upgraded the server machine from 4.7-rel to 5.0-rel, and that's when the problem reappeared. Of course, ps says that both machines are running both daemons (however, there's one extra rpc.lockd process running as user "daemon" on both machines. Normal?). I've tried everything from deleting my ~/.gconf and ~/.gconfd to recompiling gconf, but nothing seems to help. Any pointers? I'm at a loss. -Maxime Romano "Ending a sentence with a preposition is something up with which I will not put." -- Sir Winston Churchill http://www.jewcrew.org/~verbophobe/ _________________________________________________________________ Help STOP SPAM with the new MSN 8 and get 2 months FREE* http://join.msn.com/?page=features/junkmail To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-gnome" in the body of the message