Re: Another oaf race condition



> > > I looked at trying to fix this, but it's going to require some not-tiny
> > > code reorganization, I think. (If it turns out to be too annoying to fix
> > > quickly for oaf 0.x, a simple hacky solution would be to return a
> > > "TryAgain" exception and have liboaf loop until it doesn't get that...)
> > 
> > That sounds like a passable workaround.
> 
> Well, I'll leave you to do that if you want, since it looks now like we
> can "fix" evolution without even needing an oaf release by just making
> wombat always try to register every interface before exiting.

Well, I tried kludging wombat, and that wasn't working, and then I tried
adding the TryAgain hack to oafd and that wasn't working either. Someone
who understands this stuff better than I do is going to have to deal.

-- Dan



[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]