Hi, Currently the interactive service uses anonymous pipes for stdout and stderr in CreateProcess to start OpenVPN. But the service doesn't actively read from these pipes until the process exits with a non-zero error code. Any output thus read goes to the service pipe and EventLog which a casual end user never sees.
The bad side of this is the potential for deadlock which is especially bad when verb > 3: the pipe buffer may run out early causing write to block in msg (), with no or little output in the management interface. Shall we change this to use /dev/null (i.e, "NUL" on windows) for both stdout/stderr ? Selva
