Hi, On Thu, Feb 04, 2016 at 10:40:35AM -0500, Selva Nair wrote: > > (And yes, this needs to be adjusted in the installer, whichever way we > > go - globally writeable log directory, or user-individual logging) > > Its the "HKLM\OpenVPN\log_dir" key set by the installer when the service is > installed. For the automatic service, users may want it to stay at such a > system-wide location, while the interactive service does not use it > directly.
Yes, thanks. That's the key...
> But the UI (OpenVPNGUI) uses it to construct the log file path
> and passes it in the command line options.
>
> To make the log location user-dependent, we could include env variables in
> the registry key -- say %UserProfile%/OpenVPN/log But that requires the
> service to read the key as REG_EXPAND_SZ and then expand it.
>
> For now, I'll make a patch for the GUI to construct a writable log path
> when iservice is used. It looks ok to let the UI to decide where to write
> logs to.
This sounds like a good plan, thanks.
> We could document that starting openvpn using iservice needs the
> --log or --log-append option with a writable log file. If its not writable
> openvpn will fallback to stdout which will not work.
Yes, this came as a bit of surprise to me - I saw quite a bit of logging
in the status window, and then "it just stuck" (eventually I noticed the
error about the non-writeable log file in the first line, and tried making
it writeable :-) ).
gert
--
USENET is *not* the non-clickable part of WWW!
//www.muc.de/~gert/
Gert Doering - Munich, Germany g...@greenie.muc.de
fax: +49-89-35655025 g...@net.informatik.tu-muenchen.de
signature.asc
Description: PGP signature
