[omniORB] omniNames windows2000 service

[David Hyde]

This is interesting.  I've noticed on Windows 2000 that if I start omniNames
as a service (using the service controller that I've written), then close
it, the next time I try to run omniNames just from the command line it says
the following:

Read log file successfully.
Root context is
IOR:010000002b00000049444c3a6f6d672e6f72672f436f734e616d696e672f
4e616d696e67436f6e746578744578743a312e30000001000000000000002700000001010000
0e00
00003139322e3136382e38302e333900f90a0b0000004e616d6553657276696365
Error: cannot open log file 'C:\OmniOrb\etc\omninames-SHADOW.log' for
writing.

I have to manually delete the log file and the backup, then run omniNames
-start to get it working.  I'm sure that this didn't happen with NT 4.

I don't know if this is an omniNames issue, but I do wonder if the two are
connected.

Regards

David


> -----Original Message-----
> From: Lanctot, Benoit [mailto:benoit.lanctot@nrc.ca]
> Sent: 11 July 2002 14:26
> To: OmniORB Users' List (E-mail 3)
> Subject: [omniORB] omniNames windows2000 service
> 
> 
> Sorry for the silly question...
> 
> I try configuring omniNames as a NT service on windows2000, I 
> follow to the
> letter the README.win32 file and the FAQ, but it always give 
> a error message
> want I try to start the service:
> 
> Could not start the omniNames service on Local Computer.
> Error 1053: The service did not respond to the start or 
> control request in a
> timely fashion.
> 
> I try looking in the mailing list archive, but it doesn't 
> have a search
> engine anymore!
> 
> Could someone help me?
> 
> 
> Benoit
> _______________________________________________
> omniORB-list mailing list
> omniORB-list@realvnc.com
> http://www.realvnc.com/mailman/listinfo/omniorb-list
>