000503fad7
In the past, OpenRC was a hybrid of a centralized and file-scope license/copyright structure. I followed the instructions from the Software Freedom Law Center [1] to convert to a Centralized structure where possible, for easier future maintenance. [1] https://softwarefreedom.org/resources/2012/ManagingCopyrightInformation.html |
||
---|---|---|
.. | ||
down.sh | ||
README | ||
up.sh |
These handy scripts setup any dns information that OpenVPN may push. They also handle the interaction with OpenRC so that the OpenVPN service can become "inactive". This means that when it starts, it goes inactive and OpenRC continues on its merry way booting the system. When OpenVPN connects to an endpoint it then re-starts the OpenVPN service and starts up any services that depend on us. A similar thing happens when we shut down. Of course, this is all optional.