On Tue, 5 Oct 2004, Mathias Sundman wrote:
> So to summarize:
>
> SW=Service Wrapper
>
> 1. The SW should redirect stdin/stdout/stderr through a pipe.
>
> 2. The SW will write everything arriving on stdout/stderr to a logfile.
>
> 3. The SW will monitor stdout/stderr for password prompts, and
So to summarize:
SW=Service Wrapper
1. The SW should redirect stdin/stdout/stderr through a pipe.
2. The SW will write everything arriving on stdout/stderr to a logfile.
3. The SW will monitor stdout/stderr for password prompts, and when it
sees one it will send a query over the already estab
Hi all,
I agree with James for including several things such as monitoring
stdin/out/err into the wrapper.
But I'm not very ok for the idea of creating a socket for each
connection because our users will probably only use one GUI so this GUI
may have to discuss throught a unique socket to ma
On Fri, 1 Oct 2004, Mathias Sundman wrote:
> Didier announced a first release of an improved version of the OpenVPN
> Service Wrapper earlier this week. The goal with this is to allow a non
> admin user on Windows to start/stop openvpn processes.
>
> It does this by listening on a local TCP soc
Didier announced a first release of an improved version of the OpenVPN
Service Wrapper earlier this week. The goal with this is to allow a non
admin user on Windows to start/stop openvpn processes.
It does this by listening on a local TCP socket for commands like "START
config.ovpn" or "STOP c
