-
Notifications
You must be signed in to change notification settings - Fork 41
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
Delayed and sometimes incomplete log messages #11
Comments
Is it alright to use synchronous IO? I was concerned about performance, On Nov 11, 2016 23:54, "Selva Nair" notifications@github.com wrote:
|
With the logfile set to autoflush and use of exit event, loss of logs should be unlikely now. So unless anyone notices lost messages, leave it at it for now? There are two minor issues left: In my view the best option is just to redirect stdin/stderr to NUL and use "--log logfilename" or "--log-append logfilename" in the command line. Let openvpn.exe handle the log file. |
When openvpn is started by the service there is a rather long delay (up to ~1min) before messages appear in the log. When the service is stopped the log sometimes appear incomplete (using verb 4)
Especially when the config has an invlaid option and the openvpn process exits promptly, nothing appears in the log file. As openvpn flushes the output after every message, this looks like a buffering issue due to log redirection. Using --log instead of stdout redirection may be better.
The text was updated successfully, but these errors were encountered: