Hi, On Fri, Feb 12, 2016 at 8:15 AM, Gert Doering <g...@greenie.muc.de> wrote:
> Hi, > > On Fri, Feb 12, 2016 at 10:53:27AM +0200, Samuli Seppänen wrote: > > That would be good. We also need to warn about lack of permissions on > > the config files. Right now GUI just hangs if it can't read the OpenVPN > > config file. > > This is a more fundamental issue, I think - if there is something wrong > with the config file (like: syntax error, file not found, ...) OpenVPN > will exit right away, and the GUI will wait for OpenVPN's management > interface to show up, to read back the log. > > Since we know where we're sending the log file to, some enhancement to > the GUI to just go read that file in case the management interface fails > to connect (after <x> seconds?) would be good for troubleshooting. > This is tricky..First, if the config is not readable, log file is not set at that time and log goes to stdout (mapped to "/dev/null" by the GUI). Even otherwise parsing the log to figure out what went wrong is not always an easy task for a program. However, the GUI does timeout after 10 seconds or so, if the management interface doesn't come up. But the log will be empty if openvpn exited before stdout was redirected. Selva
