orbit allows one to use TCP to locate remote services, as opposed to just a local socket. This is wonderful for NFS mounted home directories with gconf. Gconf used to use this feature by saving the remote address of the gconf instance in ~/.gconfd. That way all shared computers would have the information to contact, remotely, the currently running gconf instance. However, gconf has apparently moved this file into /tmp/gconfd-$user. This has caused it to no longer function, since /tmp is not shared. So, basically, Gconf has broken the TCP functionality of Orbit. :) On Wed, 2004-03-17 at 17:48, Chipzz wrote: > On Wed, 17 Mar 2004, Jerry Haltom wrote: > > > I am having a bit of trouble trying to figure out wtf happened to TCPv4 > > support in Orbit. > > > > Adding ORBIIOPIPv4=1 to /etc/orbitrc NO LONGER WORKS. I believe it > > doesn't work because gconf is no longer creating it's lock file in the > > right location! > > > > There used to be a ~/.gconfd/lock, but there is no longer. There is now > > a /tmp/gconfd-$user though. What happened here? Was the lock moved to > > /tmp without realizing it broke TCP??? > > How can gconf break orbit when gconf depends on orbit (and NOT the other > way around)? > > kr, > > Chipzz AKA > Jan Van Buggenhout -- Jerry Haltom <jhaltom@feedbackplusinc.com> Feedback Plus, Inc.
Attachment:
signature.asc
Description: This is a digitally signed message part