How do I start a service after the network is up?

Question

In my case, squid is started before DHCP has written a new /etc/resolv.conf which results in odd errors (timeouts, 504 Gateway) when I try to load a page in the web browser.

As I see it, the correct solution would be to start squid only after dhcpd/NetworkManager/whoever (?) has finished configuring the network.

Which Ubuntu version are you using?. Or more concrete, are you using SysV or upstart?. — Javier Rivera, Mar 26 '12 at 12:20
Check: http://askubuntu.com/questions/21378/how-can-i-make-sure-one-upstart-job-starts-before-other-upstart-jobs or http://askubuntu.com/questions/3341/is-there-any-gui-tool-for-upstart — Javier Rivera, Mar 26 '12 at 12:35

score 5 · Accepted Answer · edited Apr 13 '17 at 12:23

5

You should modify the squid.conf file in /etc/init so that it only starts when network is up:

start on (started networking)

You can find much more info here, and looking at the files in your /etc/init/ dir.

This question should also help. If you prefer to configure it with a GUI, look here.

edited Apr 13 '17 at 12:23

Community

1

answered Mar 26 '12 at 12:43

Javier Rivera

35,153

score 2 · Answer 2 · answered May 05 '16 at 08:58

Here are two examples from the Upstart Cookbook:

To start a job when eth0 is available

start on net-device-up IFACE=eth0

To start once a non-loopback device has come up:

start on net-device-up IFACE!=lo

Note: net-device-up is not a regular job, it's an "Ubuntu well-known event".

How do I start a service after the network is up?

2 Answers2