[squid-users] Forcing squid to fail when the whitelist doesn't exist

[Matthew Macdonald-Wallace]

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

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

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 <http://www.mockingbirdconsulting.co.uk/>

e: info at mockingbirdconsulting.co.uk 
<mailto:matt at mockingbirdconsulting.co.uk>
t: +44 (0) 1600 717142


Bridges 
Centre,
Drybridge House,
Monmouth,
NP25 5AS

Registered in England and 
Wales, Company Number 10488438
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.squid-cache.org/pipermail/squid-users/attachments/20200707/9cd8ac97/attachment.html>