[ADDED] Running server as a Windows Service #637
Conversation
Resolves #632 Signed-off-by: Ivan Kozlovic <ivan@synadia.com>
kozlovic
force-pushed
the
run_as_windows_service
branch
from
daba4cc
to
00bf7f9
Compare
|
Maybe at the start of the service it is better to write information about the server (ServerID, Go version, nats-server version and others) into one event, rather than individual events? 21 event looks uncomfortable. |
|
I understand your concerns, however, it is not possible to do this at this stage. The logger is passed to the Store and traces about channels being recovered are traced in the Store(s) implementations. Also, NATS Streaming Server may embed the NATS Server and actually uses the NATS Server log implementation and gives that to the NATS Server embedded code to trace NATS specific events. |
|
Oh. I understood. Thanks for the work you've done. I think the functionality of the windows service will be very much not only for our company. |
|
@sharkyfm Maybe this week. Have you had a chance to try out this branch? I guess so since you reported on the logging behavior. Any other issue that you have found? |
|
Yes, I built this branch. The service is installed and uninstalled successfully, debug, trace and notice events are logged. Problems have not been found yet. |
|
Good to know. I will initiate the release likely today. Thanks! |
Bring changes from NATS Server master in. This is related to #637 Signed-off-by: Ivan Kozlovic <ivan@synadia.com>
See README for details.
Also added option to specify a Windows Event Source name (
--syslog_name),which can be helpful if running more than one service on the same machine.
Resolves #632
Signed-off-by: Ivan Kozlovic ivan@synadia.com