[omniORB] omninames 4.0.1 failing to start with log file from 3.0.3

[Clarke Brunt]

I'm upgrading our system from omniORB 3.0.3 to 4.0.1

I've done some of the programs, and they are working fine, but just tried
the new omninames.

I get immediate 'abnormal program termination' (this is on Windows NT4) if I
start it with no arguments and it finds the log file from the previously
running v3.0.3 version. If I 'hide' the old log file, then I can start it
with '-start', and can then stop and restart with no arguments as needed.

Any ideas? Is it a bug or a 'feature'? I guess that the 'abnormal program
termination' might be a bug, even if it _isn't_ supposed to work with the
old log files.

I don't really mind having to start afresh with a new log file, but this
will mean a less smooth upgrade, as I will have to re-start everything else
in order to re-populate the naming service.

--
Clarke Brunt