[omniORB] Stopping omniNames and omniEvents

[Paul Nader]

Michael,

I thought you might be interested in knowning I've discovered a bug in omniEvents

which prevents it from backing up its log file (it stops after the first backup).
It
doesn't actually affect the log file but it means that it  can grow a lot quicker
(the
backup process scrubs all of the redundant information out of the original file).

The next release (due sometime early next week) will contain a fix for it.

Cheers, Paul.

Paul Nader wrote:

> The persistency in omniEvents is based on the scheme used by omniNames so
> its also transactional. Use kill -9.
>
> Rgds, Paul.
>
> Sai-Lai Lo wrote:
>
> > >>>>> Michael J Donahue writes:
> >
> > > How do you end omniNames and omniEvents on Unix and Windows?  I have been
> > > simply doing a kill -9(or equiv) on the processes, but is the best way?
> > > II haven't actually checked, but I would guess there might be a SigTerm
> > > handler in the code to handle this situation.  Wouldn't it be better to
> > > use some sort of stop file, or something?
> >
> > Kill -9 will do for omniNames. Updates to the persisent store is
> > transactional so it doesn't hurt if omniNames is killed any time.
> >
> > I guest the same for omniEvents but this has
> > to be confirmed by Paul.
> >
> > Sai-Lai
> >
> > --
> > Sai-Lai Lo                                   S.Lo@uk.research.att.com
> > AT&T Laboratories Cambridge           WWW:   http://www.uk.research.att.com
> > 24a Trumpington Street                Tel:   +44 1223 343000
> > Cambridge CB2 1QA                     Fax:   +44 1223 313542
> > ENGLAND