Hi, On Fri, Dec 18, 2015 at 09:08:20PM -0000, debbie...@gmail.com wrote: > With the proviso that there is not a subsequent line such as: > setenv opt something_else
No. All "setenv opt" lines are totally independent.
Basically, the setenv opt hack does this:
/*
* If directive begins with "setenv opt" prefix, don't raise an error if
* directive is unrecognized.
*/
if (streq (p[0], "setenv") && p[1] && streq (p[1], "opt") &&
!(permission_mask & OPT_P_PULL_MODE))
{
p += 2;
msglevel_fc = M_WARN;
}
"move the messagelevel (from M_FATAL) to M_WARN, and proceed with parsing
this line to the keyword after 'opt'" (p[2]).
I'm not totally sure on the OPT_P_PULL_MODE part - it's possible that
"setenv opt" doesn't work when pushed, but then, pushed options never
cause M_FATAL anyway. Someone should test and document this :-)
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
------------------------------------------------------------------------------
_______________________________________________ Openvpn-users mailing list Openvpn-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/openvpn-users
