Perfect! The following worked:
I defined openvpn_plugin_select_initialization_point_v1() to return
OPENVPN_PLUGIN_INIT_POST_DAEMON and now it all works since the plugin
invocation now gets delayed to be after the daemon thread starts up.
Thanks a lot,
Vineet
On Thu, Jun 24, 2010 at 4:58 AM, chant
> The reason is obviously the fact that the thread-creation occurred
> *before* the daemon() call (that forked off a child which has no way
> of inheriting a copy of that thread).
> So does this mean then that the ovpn daemon infrastructure will only
> work with plugins that don't do threading of t
Hi,
I am writing a plugin that creates a thread at plugin-open time. But
when I start ovpn as a daemon the ovpn code has no knowledge of that thread.
The reason is obviously the fact that the thread-creation occurred
*before* the daemon() call (that forked off a child which has no way
of inheritin
