epinephrine
Hello!
The --daemon option sends the process into background too early for my systemd setup. From what the man page says I hoped that daemonization happens after I see "Initialization Sequence Completed" in the system logs. But it happens earlier.
My shorewall firewall systemd service depends on my openvpn service, and is set to start after it. Well, "after" means here, as soon as openvpn daemonizes. But that happens before "Initialization Sequence Completed". Why? Is there a way to block until this event happens?
Background: My shorewall setup block all request outside the vpn tunnel, i.e., also DNS requests to my isp's router. But after openvpn daemonizes, it needs to resolv the hostname of my vpn provider. And the IPs are dynamic, so I cannot switch to a static ip. Here openvpn hangs and cannot open the vpn connection and shorewall is already up. But after the vpn tunnel is up, I don't want to allow any DNS traffic to go to my ISP's router.
Looking forward to your suggestions!
