Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[FIXED] Windows Service: do not force usage of syslog #1025

Merged
merged 1 commit into from
Mar 10, 2020
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion nats-streaming-server.go
Original file line number Diff line number Diff line change
Expand Up @@ -115,7 +115,7 @@ Embedded NATS Server Options:
Logging Options:
-l, --log <string> File to redirect log output
-T, --logtime=<bool> Timestamp log entries (default: true)
-s, --syslog <string> Enable syslog as log method
-s, --syslog <bool> Enable syslog as log method
-r, --remote_syslog <string> Syslog server addr (udp://localhost:514)
-D, --debug=<bool> Enable debugging output
-V, --trace=<bool> Trace the raw protocol
Expand Down
2 changes: 1 addition & 1 deletion server/service_windows.go
Original file line number Diff line number Diff line change
Expand Up @@ -131,7 +131,7 @@ func Run(sOpts *Options, nOpts *natsd.Options) (*StanServer, error) {
}
if isInteractive {
run = debug.Run
} else {
} else if nOpts.Syslog || nOpts.LogFile == "" {
sysLogInitLock.Lock()
// We create a syslog here because we want to capture possible startup
// failure message.
Expand Down