|
|
On Sun, 4 Jul 2004, sam wrote:
I would rather go for automtic configuration for RoadWorriors rather than
useing complicated managment tool like this.
Remember our goal is to simplify user's administration.
Could you please elaborate what you mean with "complicated management
tool"?
What we are discussing is just how the gui client should communicate with
it's openvpn processes "behind the scene". The graphical interface the
user sees should still be as simple as possible.
Do you consider the current "look" of my gui complicated?
Mathias Sundman wrote:
On Sun, 4 Jul 2004, Tyrone Omidi wrote:
How about options manage the service?
How would you like to see this implemented? Just another menu item that
can start/stop the service?
What about multiple configs started by the service. Should the GUI be able
to start/stop these individually? How do we do this?
When we have the "management protocol" ready we should be able to use this
to hook into the processes started by the service.
To be able to stop a process started by the service and then start it
again, we would need either:
1. A "SUSPEND" mode in openvpn, so we can tell it to "stop", but the
process should still be running, but inactive, so we later can tell it to
start again (still running as the same user as the service wrapper started
it as.).
2. What Jan Kiszka suggested, an openvpn process running capable of
forking of new processes with a specific config-file.
--
_____________________________________________________________
Mathias Sundman (^) ASCII Ribbon Campaign
NILINGS AB X NO HTML/RTF in e-mail
Tel: +46-(0)8-666 32 28 / \ NO Word docs in e-mail
____________________________________________
Openvpn-users mailing list
Openvpn-users@xxxxxxxxxxxxxxxxxxxxx
https://lists.sourceforge.net/lists/listinfo/openvpn-users
|