Support for MX and antiX Linux distros
http://forum.mxlinux.org/
Which is good. So what's left, I assume, is to startup the daemon earlier
Code: Select all
# leave onle one line uncommented
/opt/mullvad-vpn/resources/mullvad-daemon -v --disable-stdout-timestamps
#
/usr/bin/env qomui-service
Code: Select all
#!/bin/sh -e
#
# rc.local
#
# This script is executed at the end of each multiuser runlevel.
# Make sure that the script will "exit 0" on success or any other
# value on error.
#
# In order to enable or disable this script just change the execution
# bits.
#
/opt/mullvad-vpn/resources/mullvad-daemon -v --disable-stdout-timestamps
exit 0
Code: Select all
#!/bin/sh -e
#
# rc.local
#
# This script is executed at the end of each multiuser runlevel.
# Make sure that the script will "exit 0" on success or any other
# value on error.
#
# In order to enable or disable this script just change the execution
# bits.
#
/usr/bin/env qomui-service
exit 0
I think i've done it right, but nothing changed. BTW i'm testing it in vm, not to worry about bricking anything in my main system.fehlix wrote: ↑Tue Sep 25, 2018 11:45 am Perhaps - at least for a test - try to start the daemon as this.
Do add those lines add the end of the file /etc/rc.local
Keep only one line un-commented either for mullvad-daemon or for qomui-service - not both.
Make sure the last line will be exit 0 followed by a new line.So the file /etc/rc.local looks either like thisCode: Select all
# leave onle one line uncommented /opt/mullvad-vpn/resources/mullvad-daemon -v --disable-stdout-timestamps # /usr/bin/env qomui-service
for mullvad-daemonor like this for qomui-serviceCode: Select all
#!/bin/sh -e # # rc.local # # This script is executed at the end of each multiuser runlevel. # Make sure that the script will "exit 0" on success or any other # value on error. # # In order to enable or disable this script just change the execution # bits. # /opt/mullvad-vpn/resources/mullvad-daemon -v --disable-stdout-timestamps exit 0EDIT: and do reboot after those changes ...Code: Select all
#!/bin/sh -e # # rc.local # # This script is executed at the end of each multiuser runlevel. # Make sure that the script will "exit 0" on success or any other # value on error. # # In order to enable or disable this script just change the execution # bits. # /usr/bin/env qomui-service exit 0
Yeah, it's probably too late with rc.local at the end of the runlevel, it needs to be get started earlier.
Look i'm not that stupid. I did what you said first and after that i started mullvad, but same thing happened.fehlix wrote: ↑Wed Sep 26, 2018 6:20 pmYeah, it's probably too late with rc.local at the end of the runlevel, it needs to be get started earlier.
So what is needed would be to have init.d start script to get it a bit earlier started.
You might look whether you can find any mullvad related service files, which we might convert
to inti.d scripts.
There is a file named "mullvad-daemon.service" and that is inside:fehlix wrote: ↑Thu Sep 27, 2018 11:52 am OK, I meant if you look for mullvad servcice files within the systemd folder /etc/systemd/system.
And if you post those here we might convert them into alternative start files,
so they get started ealier than rc.local, which appreaas to be to late, when you start MX17 with the default SysVint start system.
I can't test this myself, as I have no mullvad vpn.
Code: Select all
/opt/Mullvad\ VPN/resources/mullvad-daemon -v --disable-stdout-timestamps