Hrm... Easy enough to test. Is there a way to disable that behavior? Or even just change the timeout? Why would I want that anyways?
Thanks! On Wed, 2003-08-20 at 10:38, Jason A. Pfeil wrote: > I don't think this is an NFS lock problem. From your description, you are > running a GNOME 2.x-based desktop. That uses gconfd, a program to manage > configuration information. Gconfd does *not* exit when you log out. It > waits like five minutes in case you log in again. So, it is holding its > own lockfile open. If you log out and then log back in at the text > console and issue a gconftool-2 --shutdown you will be able to log in at > another machine. > > Alternatively, wait the five minutes for it to shut itself down. :-) > > --Jason > > On 17 Aug 2003, Matt Neimeyer wrote: > > > Hey all, > > > > I've got three machines at home all running the same versions of > > everything (so far as I can tell). Machine A is running NFS and > > exporting several home directories. If I go to Machine B first and log > > on to my profile it works but when I log out and walk over to Machine C > > it gives me the following error. > > > > Please contact your system administrator to resolve the following > > problem: Could not resolve the address "xml:readwrite:/home/matt/.gconf" > > in the configuration file "/etc/gconf/2/path": Failed to lock > > '/home/matt/.gconf/%gconf-xml-backend.lock/ior': probably another > > process has the lock, or your operating system has NFS file locking > > misconfigured (Resource temporarily unavailable) > > > > If I go to either Machine B or Machine C first it works. If I log out > > then reboot I can go anywhere. If I don't reboot the first machine I log > > in to I can't log in anywhere else. This is for any profile and any > > order of machine log in/out. > > > > Any advice would be greatly appreciated. > > > > Matt > > > > > > -- > > [EMAIL PROTECTED] mailing list > > > > -- [EMAIL PROTECTED] mailing list
