corndog

If you have been having an issue with things not running on boot when enabled in the GUI, I have found that creating cron jobs in the terminal are effective. I was able to manually start the OpenVPN module, but it would not start automatically on reboot. When you start a service, the GUI usually tells you the PSID(Process ID). To view it in the terminal, just use the "ps" command. Then you can see the command used by the system to start the module. For example: The OpenVPN module process is shown as - /usr/bin/openvpn --daemon --configure /etc/openvpn/my-vpn.conf Use nano to create and edit a file. - nano "myfile.sh" The specific command in this example is openvpn --daemon --configure /etc/openvpn/my-vpn.conf which just takes away the path from the command. Save the file with CTRL+O Exit the file with CTRL+X Make the file executable with chmod +x "myfile.sh" Use crontab -e, which will put you into a text editor like vi. Type "i" to enable insert mode. Then specify the time you would like this command to run, followed by your shell script @reboot /"path-to-your-file"/"myfile.sh" To exit and save press ESC, then type :"wq", and then Enter Going through this process might help you further understand how Linux works. Figuring this out was definitely a rewarding experience for me. This concept should also work with any other modules that you are able to manually start, but will not start automatically after a reboot.