arch linux not firing correctly

  • Posted May 20, 2013

I’ve got a couple of services that rely on a network connection starting with systemd. I’ve had them starting correctly on other servers by using I’ve also tried but neither are working on here. I have a feeling both are firing before a network connection has started. Thus things are starting, not able to lock onto their port and are dying on boot. Any thoughts?


Submit an answer
You can type!ref in this text area to quickly search our full set of tutorials, documentation & marketplace offerings and insert the link!

These answers are provided by our Community. If you find them useful, show some love by clicking the heart. If you run into issues leave a comment, or add your own answer to help others.

Hm. It’s a solution but I’d much rather do it right. I’m more worried about the underlying problem of such an important part of systemd not doing what it should and the effects that might be having elsewhere.

Try adding them in the very bottom of /etc/rc.local* so they’re the last thing that is started which would mean they’re started after networking is. <br> <br>*systemd ignores /etc/rc.local - please see