Squid proxy - success!!!!!
Many, many thanks for all your help and advice in setting up my Linux proxy server. I had a parents' evening tonight which started at 6.00 pm, so I stayed after school and set about configuring squid. The main problem I had was that I didn't notice that a small part of the /etc/squid.conf was *not* commented out - glancing through the file I thought it was all commented out and the bit which wasn't dealt with access control. I was managing to access the squid proxy from another workstation, but could not get any further than an error message telling me I did not have authorisation. Once I spotted this, I had squid working within a few minutes. You know that feeling when you've cracked it - sheer elation! I shall now be looking for tweaks etc. to make the whole thing work even better!! -- Phillip Deackes Using Storm Linux
Hi,
The main problem I had was that I didn't notice that a small part of the /etc/squid.conf was *not* commented out - glancing through the file I
Just as a minor point, but presuming that comments in squid.conf are the same as other comments files and preceded by a # (hash) symbol remember that grep -v ^# is your friend, and worth doing on long config files that sometimes have lines over the width of a standard console ( i.e. inetd.conf ). I expect you already know how to do this, but just making this point that this is one of the commands I run when I've reached the "well, I'm sure I've covered everything" stage :) -- warnendes warnendes dieser Programmsatz bedeutet nicht nichts Sent through GMX FreeMail - http://www.gmx.net
Just as a minor point, but presuming that comments in squid.conf are the same as other comments files and preceded by a # (hash) symbol remember
----- Original Message -----
From: Nick Drage
grep -v ^#
is your friend, and worth doing on long config files that sometimes have lines over the width of a standard console ( i.e. inetd.conf ).
I expect you already know how to do this, but just making this point that this is one of the commands I run when I've reached the "well, I'm sure
I've
covered everything" stage :)
Thanks for that tip, Nick - I'll be making much use of it. Along the same lines of useful tricks here are a couple that were taught to me recently: tail -f /usr/local/squid/logs/access.log is a good one to run in a terminal window on the same screen in which you are using a browser while testing Squid. tail displays the latest lines added to access.log and the -f means that tail "follows" the log file as it grows. ps -ef | squid will tell you if squid is actually running and gives you its PID number. I jot these sort of things down in a notebook because when I first learn them and use them a lot I'm sure I'll never forget them but I've learnt from bitter experience that I'm quite capable of doing so. Anyone got any other useful tips? Nigel. St. John's School, Northwood
participants (3)
-
Nick Drage -
npauli -
Phillip Deackes