[omniORB] Error execute: notifd

Robert E. Gruber gruber at research.att.com
Wed Sep 10 11:46:29 BST 2003


If you do not want notifd to register with the naming service, use the
-n option.

The documentation for notifd is at:

http://www.research.att.com/~ready/omniNotify/nfy_doc_notifd_config.html

The top-level document page is:

http://www.research.att.com/~ready/omniNotify/nfy_documentation.html

-----Original Message-----
From: omniorb-list-bounces at omniorb-support.com
[mailto:omniorb-list-bounces at omniorb-support.com] On Behalf Of
croonen.davy at pandora.be
Sent: Wednesday, September 10, 2003 10:37 AM
To: omniorb-list at omniorb-support.com
Subject: [omniORB] Error execute: notifd 

Hi everybody,

Now that omniNotify-2.0 compiled fine (thanks to: Rene Jager and Duncan
Grisby) with omniORB-4.0.2, I encountered the following error while
executing notifd:

[kassa at edmpc10 src]$ notifd -c omniNotify/standard.cfg
 
omniNotify: NO_RESOURCES exception while trying to find the NameService
 
DBG[lib/FilterAdmin_i.cc:124]: ** Internal error:
RDI_OPLOCK_DESTROY_CHECK : FilterFactory_i 0x8068120 allocated
OplockEntry has not been freed properly
 
notifd: failed to create a new omniNotify server
[kassa at edmpc10 src]$

Does somebody has a solution to this problem?


Greetz
Davy Croonen


_______________________________________________
omniORB-list mailing list
omniORB-list at omniorb-support.com
http://www.omniorb-support.com/mailman/listinfo/omniorb-list




More information about the omniORB-list mailing list