On Wed, 7 Jul 2004, James Yonan wrote:
On Tuesday 06 July 2004 16:58, Mathias Sundman wrote:
Some more things to consider...
1. On Windows, if the the service wrapper has started some openvpn
processes before our gui agent is started, how should find out about
those processes?
I can think of
On Thursday 08 July 2004 02:55, Mathias Sundman wrote:
> On Wed, 7 Jul 2004, James Yonan wrote:
> > On Tuesday 06 July 2004 16:58, Mathias Sundman wrote:
> >> Some more things to consider...
> >>
> >> 1. On Windows, if the the service wrapper has started some openvpn
> >> processes before our gui a
On Thu, 8 Jul 2004, James Yonan wrote:
1. On Windows, if the the service wrapper has started some openvpn
processes before our gui agent is started, how should find out about
those processes?
I think that the goal here is to work towards putting all of the complexity
into the portable service
> > >> 1. On Windows, if the the service wrapper has started some openvpn
> > >> processes before our gui agent is started, how should find out about
> > >> those processes?
> > >>
> > >> I can think of the following ways:
> > >>
> > >> 1a. Ask the service wrapper via the socket interface that I'm
On Thu, 8 Jul 2004, Denis Vlasenko wrote:
1. On Windows, if the the service wrapper has started some openvpn
processes before our gui agent is started, how should find out about
those processes?
I think it's an important point worth some discussion on whether to (a)
put all the "intelligence"
On Friday 09 July 2004 00:35, Mathias Sundman wrote:
> > What I am trying to say? I am very happy that you guys are actively
> > working on openvpn. Really.
> >
> > Just please do not OVERdesign it.
> >
> > Maybe it's better to try to port daemontools to Windows
> > and run openvpn daemon(s) under
