02-19-2021, 02:56 PM
rc.local is a relic from the times of init times. It was available for a time when the transition from init to systemd has been performed but nowadays rc.local is no longer really a thing.
It looks like systemd has a rc.local compatible interface. So that means that you can most likely simply create a empty rc.local file in /etc and fill it with your code which should be run by systemd.
Have you tried that already? Just creating the rc.local file yourself? Even in the times of init or the transition time of systemd the rc.local file was usually empty or only contained comments. So nothing you can really break.
Apart from that why do you think that rc.local is the issue? You post that openvpn service returns an error but you didn't provide the journald entry with that error. Did you forget the include that information and there you found the rc.local issue?
It looks like systemd has a rc.local compatible interface. So that means that you can most likely simply create a empty rc.local file in /etc and fill it with your code which should be run by systemd.
Have you tried that already? Just creating the rc.local file yourself? Even in the times of init or the transition time of systemd the rc.local file was usually empty or only contained comments. So nothing you can really break.
Apart from that why do you think that rc.local is the issue? You post that openvpn service returns an error but you didn't provide the journald entry with that error. Did you forget the include that information and there you found the rc.local issue?
![[Image: zHHqO5Q.png]](https://i.imgur.com/zHHqO5Q.png)
