Date: Thu, 14 Apr 2005 11:29:46 +0200 From: =?ISO-8859-1?Q?Anders_Trob=E4ck?= <gnome@troback.com> To: freebsd-gnome <freebsd-gnome@freebsd.org> Subject: Re: Gedit failed to lock Message-ID: <425E380A.6030807@troback.com> In-Reply-To: <4256473E.3050901@troback.com> References: <424EA0B1.8010203@troback.com> <1112481822.65127.1.camel@shumai.marcuscom.com> <42540D30.2040103@troback.com> <1112807950.84273.10.camel@shumai.marcuscom.com> <42542AA6.50203@troback.com> <1112813229.84273.29.camel@shumai.marcuscom.com> <42558CD1.8090003@troback.com> <1112941275.76371.36.camel@shumai.marcuscom.com> <4256473E.3050901@troback.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Found a workaround for my problem! Maybe not the most beautiful but it works for me: touch /tmp/.recently-used_username ln -s /tmp/.recently-used_username ~/.recently-used \\anders Anders Troback wrote: > OK. thanks! > > I will try to find out why...if I find a soluton I let you know! > > \\anders > > Joe Marcus Clarke wrote: > >> On Thu, 2005-04-07 at 21:41 +0200, Anders Troback wrote: >> >>> I removed the file but no luck:-( >> >> >> >> Sorry, I don't any any other suggestions. I use gedit with NFS >> everyday, and I've never seen these lock failures after I enabled >> rpc.lockd and rpc.statd. >> >> Joe >> >> >>> \\anders >>> >>> Joe Marcus Clarke skrev: >>> >>> >>>> On Wed, 2005-04-06 at 20:29 +0200, Anders Troback wrote: >>>> >>>> >>>> >>>>> Yes I did! Tryed too start it manaly but no luck so I did a reboot... >>>>> >>>> >>>> >>>> It works for me over NFS here. You might try the other suggestion of >>>> periodically zeroing out the ~/.recently-used file. >>>> >>>> Joe >>>> >>>> >>>> >>>> >>>>> Joe Marcus Clarke skrev: >>>>> >>>>> >>>>> >>>>>> On Wed, 2005-04-06 at 18:24 +0200, Anders Troback wrote: >>>>>> >>>>>> >>>>>> >>>>>> >>>>>>> Maybe not for this list but how do you enable rpc_lockd? >>>>>>> >>>>>>> I entered rpc_lockd_enable="YES" in /etc/rc.conf on both NFS >>>>>>> server and NFS client but no change. >>>>>>> >>>>>>> Gedit is not alone, many apps do the same... >>>>>>> >>>>>>> >>>>>>> >>>>>> >>>>>> >>>>>> Did you reboot both machines after doing this? >>>>>> >>>>>> Joe >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> >>>>>>> \\anders >>>>>>> >>>>>>> Joe Marcus Clarke wrote: >>>>>>> >>>>>>> >>>>>>> >>>>>>> >>>>>>>> On Sat, 2005-04-02 at 15:40 +0200, Anders Troback wrote: >>>>>>>> >>>>>>>> >>>>>>>> >>>>>>>> >>>>>>>>> Hi all! >>>>>>>>> >>>>>>>>> I'm new to the list so bare with me! >>>>>>>>> >>>>>>>>> When I'm running gedit over XDMCP I got a: >>>>>>>>> >>>>>>>>> WARNING **: Failed to lock: Operation not supported >>>>>>>>> >>>>>>>>> After a few seconds gedit starts and works just fine. >>>>>>>>> >>>>>>>>> If I run it as root or as a user on the console (XDM on the >>>>>>>>> server), no warning and the program starts instantly. >>>>>>>>> >>>>>>>>> I noticed this problem in 2.8 and it still exists in 2.10. Only >>>>>>>>> tried on 5.3-STABLE and 5.4-PRERELEASE. >>>>>>>>> >>>>>>>>> Not a big problem but the seconds feels like a decade:-) >>>>>>>>> >>>>>>>>> >>>>>>>> >>>>>>>> >>>>>>>> Chances are you're running off of an NFS volume. In which case, >>>>>>>> both >>>>>>>> the NFS server and client must be running rpc.lockd. >>>>>>>> >>>>>>>> Joe >>>>>>>> >>>>>>>> >>>>>>>> >>>>>>>> >>>>>>>> >>>>>>>>> \\anders >>>>>>>>> >>>>>>>>> >>>>>>>>> >>> >>> > -- ============================================ Microsoft is not the answer. Microsoft is the question. And 'No' is the answer! -------------------------------------------- Anders Trobäck http://www.troback.com
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?425E380A.6030807>