Re: stale IORs in lock directory ...
- From: Michael Meeks <michael ximian com>
- To: Havoc Pennington <hp redhat com>
- Cc: <gconf-list gnome org>
- Subject: Re: stale IORs in lock directory ...
- Date: Mon, 13 Aug 2001 20:39:24 -0400 (EDT)
Hi Havoc,
On 13 Aug 2001, Havoc Pennington wrote:
> Are you considering that I ping the existing lock holder by invoking
> the _ping() method on it?
There is really not much need for a ping, a simple
CORBA_Object_non_existant will tell you whether the other end is accepting
communications - or points at a now defunct server.
> I'm not sure I've figured out which code path you're describing -
> you're saying that if a server exists and we pass the old one to oaf,
> it doesn't end up owning the lock? Didn't it already have the lock?
Um - well, possibly - but it's quite possible that the server
mentioned in ~/.gconfd is actualy dead - and it's good to check for that
before giving it's IOR to oaf and exiting.
> This whole mess is just a workaround for OAF "losing" gconfd anyhow,
> so I wish it could go away.
It is well worth fixing the bug in the right place IMHO, then we
might get a fix that is genericaly useful to other programs, and not
leave an ugly - not understood race / fault in the underlying system -
which sucks.
Regards,
Michael.
--
mmeeks gnu org <><, Pseudo Engineer, itinerant idiot
[
Date Prev][
Date Next] [
Thread Prev][
Thread Next]
[
Thread Index]
[
Date Index]
[
Author Index]