Re: gconfd and multiple machines

[Owen Taylor <otaylor redhat com>]

On Tue, 2003-05-06 at 16:18, Havoc Pennington wrote:
> On Tue, May 06, 2003 at 04:16:23PM -0400, seth vidal wrote: 
> > curiously enough if you take the other tack and make gconfd put its lock
> > files in /tmp you end up with all sorts of oddities on rhl 9.
> > 
> > if I set that up on a user. then login to a single machine as that user
> > then settings changes won't take place for that user until I logout,
> > after that they are ok, but they do odd things when you login to
> > multiple machines. It's like the last-written semantic is only partially
> > true.
> > 
> > I can send more debug logs if anyone is interested in the strange and
> > wonderful errors I received.
> 
> I'm interested in what goes wrong with the local locks - assuming you
> switch to local locks with all apps/gconfd exited, I wouldn't expect
> too much weirdness (unless you go back and forth between the machines
> changing stuff on each as fast as you can).

As I was saying the other day, I don't think "as fast as you can"
is necessary to get a corrupt database.

The best that writing the files atomically does is give you coherency
between the keys in a single directory. But that isn't enough:
it should be easy, for instance, to get
apps/gnome-terminal/default_profile pointing at a non-existent profile.

Regards,
                                          Owen