Tuesday, April 30, 2024
 Popular · Latest · Hot · Upcoming
5
rated 0 times [  5] [ 0]  / answers: 1 / hits: 15060  / 1 Year ago, mon, may 22, 2023, 11:39:58

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.


More From » startup

 Answers
4

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.


[#39659] Wednesday, May 24, 2023, 1 Year  [reply] [flag answer]
Only authorized users can answer the question. Please sign in first, or register a free account.
fectlyole

Total Points: 64
Total Questions: 110
Total Answers: 110

Location: Nicaragua
Member since Thu, Feb 3, 2022
2 Years ago
fectlyole questions
Sun, May 8, 22, 02:54, 2 Years ago
Mon, Jun 21, 21, 16:56, 3 Years ago
Fri, Jul 9, 21, 17:44, 3 Years ago
;