Search squid archive

Forcing squid to fail when the whitelist doesn't exist

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Hey all,

We're re-configuring a squid proxy solution for a client and as part of it we made the assumption that squid would fail if we asked it to read a whitelist that wasn't present.

We've now discovered that Squid fails to read the file, throws an error in the log ( Error: Cannot open file /etc/squid/whitelist.txt for reading ), and then starts up anyway and listens on port 3128 but without the whitelist present.

I've also discovered the "-C" flag that helps us ignore even more serious issues, however I can't find anything either in the documentation or by searching that shows us how to make squid stop as soon as it encounters an error.

Is this possible? I've searched the FAQ and various other sources, but of course "stop squid from starting when error" or similar just returns a load of results about how to fix various errors that stop squid from starting, rather than deliberately wanting Squid to fail.

Thanks in advance,

Matt


--
Matthew Macdonald-Wallace MIET
Co-Founder
Mockingbird Consulting
Connecting you with your environment


Bridges Centre,
Drybridge House,
Monmouth,
NP25 5AS

Registered in England and Wales, Company Number 10488438


--
Mockingbird Consulting
Connecting you with your environment

w: www.mockingbirdconsulting.co.uk
e: info@mockingbirdconsulting.co.uk
t: +44 (0) 1600 717142

Bridges Centre,
Drybridge House,
Monmouth,
NP25 5AS

Registered in England and Wales, Company Number 10488438
_______________________________________________
squid-users mailing list
squid-users@xxxxxxxxxxxxxxxxxxxxx
http://lists.squid-cache.org/listinfo/squid-users

[Index of Archives]     [Linux Audio Users]     [Samba]     [Big List of Linux Books]     [Linux USB]     [Yosemite News]

  Powered by Linux