On Mon, Feb 26, 2018 at 13:57:11 -0500, Daniel Kahn Gillmor wrote: > On Mon 2018-02-26 16:28:19 +0100, David Woodhouse wrote: > > > > Does the same approach with work openconnect? Or could we do it with an > > exported environment variable instead? > > i don't know whether the same approach works with openconnect, sorry. Yes, openconnect --script "/path/to/vpnc-script --foo" does work. > fwiw, i'd be happy with either approach. With an exported env var, i If this is done with an env var, it might be nice to namespace it somewhat, like VPNC_SCRIPT_NO_UPDATE_RESOLVCONF. > assume the line would just be something like: Using an env var also opens the possibility of setting it in the parent shell or .service file or whatever. -- mike -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 833 bytes Desc: not available URL: <http://lists.infradead.org/pipermail/openconnect-devel/attachments/20180226/ce476b35/attachment.sig>
