Date: 25 Feb 2003 00:38:29 -0500 From: Joe Marcus Clarke <marcus@marcuscom.com> To: Maxime Romano <verbophobe@hotmail.com> Cc: FreeBSD GNOME Users <gnome@freebsd.org> Subject: Re: Gconf and NFS homedirs Message-ID: <1046151509.48782.137.camel@shumai.marcuscom.com> In-Reply-To: <F89ydC3hSsxLtBH49KO0004a887@hotmail.com> References: <F89ydC3hSsxLtBH49KO0004a887@hotmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
--=-riZRXMBb5EHk6A3+1wGa Content-Type: text/plain Content-Transfer-Encoding: quoted-printable On Tue, 2003-02-25 at 00:25, Maxime Romano wrote: > Morning, >=20 > Upon startup of a gnome session, gconf complains that it can't lock the f= ile=20 > ~/.gconf/%gconf-xml-backend.lock/ior . So, making sure that gconf isn't=20 > running, I delete that nasty file, and restart gnome. It seems to really= =20 > want to start, but then it outputs hundreds of messages to /var/log/messa= ges=20 > explaining that it can't lock ~/.gconfd/lock/ior, and the whole session g= oes=20 > haywire. Once that file is deleted, gconf will start without complaining= ,=20 > and the session will continue as normal. >=20 > 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),= =20 > it's caused by my NFS mounted home directory, and that fact that rpc.stat= d=20 > and rpc.lockd aren't running on both machines. >=20 > Now, I first (gasp!) had this problem when I upgraded the client machine = to=20 > 5.0-rel. At that time, the rpc processes weren't started on either=20 > machines. I stuck rpc_statd_enable=3D"YES" and rpc_lockd_enable=3D"YES" = in=20 > rc.conf on both machines and everything went back to normal. Yesterday,=20 > however, I upgraded the server machine from 4.7-rel to 5.0-rel, and that'= s=20 > when the problem reappeared. Of course, ps says that both machines are=20 > running both daemons (however, there's one extra rpc.lockd process runnin= g=20 > as user "daemon" on both machines. Normal?). >=20 > I've tried everything from deleting my ~/.gconf and ~/.gconfd to recompil= ing=20 > gconf, but nothing seems to help. Any pointers? I'm at a loss. I heard there were some NFS locking issues in 5.x that affect GNOME.=20 That's the main reason I haven't upgraded any of my home machines. It works just fine with -STABLE. Of course, I don't run rpc.lockd on -STABLE since it's broken. I only run rpc.statd on my NFS servers. You may want to poke around the current@ archives for more clues. Joe >=20 > -Maxime Romano > "Ending a sentence with a preposition is something up with which I will n= ot=20 > put." > -- Sir Winston Churchill > http://www.jewcrew.org/~verbophobe/ >=20 > _________________________________________________________________ > Help STOP SPAM with the new MSN 8 and get 2 months FREE* =20 > http://join.msn.com/?page=3Dfeatures/junkmail >=20 >=20 > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-gnome" in the body of the message --=20 PGP Key : http://www.marcuscom.com/pgp.asc --=-riZRXMBb5EHk6A3+1wGa Content-Type: application/pgp-signature; name=signature.asc Content-Description: This is a digitally signed message part -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.1 (FreeBSD) iD8DBQA+WwFVb2iPiv4Uz4cRAso1AJ9LI+f8OJv8r5uodCl02KbDI9KsAQCdGOmu Allaoz06beQaCrlARU+tph4= =hWr7 -----END PGP SIGNATURE----- --=-riZRXMBb5EHk6A3+1wGa-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-gnome" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?1046151509.48782.137.camel>