[omniORB] Name service problems

[Michael]

omninames is non-valatile by default. It normally stores information in
/var/log/omninames-<hostname>.[log|bak] which needs to be writable by
the user running the process.

You can override this location by putting OMNINAMES_LOGDIR in the
environment or by specifying -logdir <directory> on the command line.

We're running omniNames out of daemontools (http://cr.yp.to) to make
sure it restarts on crashes - but we've yet to see one of these :)

Roger wenham wrote:
> Hi,
> 
> I am having problems with omniNames stopping for no apparent reason.
> 
> This happens about once a week, on various Solaris machines. 
> 
> Has anyone else seen this behaviour, if so, I would be grateful for any pointers 
> on how to go about debugging this.
> 
> The start command looks like this
> /opt/omniORB/bin/omniNames -errlog /opt/log/omniName.log
> 
> There are no errors to be found in the omniName.log.
> 
> A second question is: When I re-start the name server after an error, it has of course
> forgotten all the names registered with it. I have searched the documentation for the
> way to make the name server non volatile, but have found nothing so far. 
> 
> Can some kind soul enlighten me please...
> 
> Thanks in advance
> 
> Roger
> 
>