[squid-users] manual proxy configuration ...

[Albretch Mueller]

On 5/29/21, Antony Stone <Antony.Stone at squid.open.source.it> wrote:
> I think this is a question for the Knoppix packagers; we don't know what
> they
> did to break Squid in this way.

 OK, I will try all the steps again but first I will remove the
installed squid version that comes with knoppix

On 5/29/21, Matus UHLAR - fantomas <uhlar at fantomas.sk> wrote:
> standard port for squid, makes squid listen on port 3128 of all available
> interfaces.
> If that's your local machine, localhost (3128) is one of those and if you
> want to stop others from accessing it, you can configure
>
> http_port localhost:3128

 Thank you, I will try that.

> it's possible that squid was compiled without unlinkd support. In such case,
> you don't need that directive.
>
> we can guess that unlinkd lives in /media/knoppix/squid3/4.15/sbin/unlinkd
> or somewhere under /media/knoppix/squid3/4.15 directory

 from:

 https://www.oreilly.com/library/view/squid-the-definitive/0596001622/re58.html

 Name: unlinkd_program

 Synopsis: This is the pathname to the unlinkd program. By executing
the unlink operations in this external process, Squid’s performance
improves significantly. You can disable the external unlinker with the
—disable-unlinkd option to ./configure.

 Default: unlinkd_program $prefix/libexec/unlinkd
~
 but in my $prefix I don't see that folder:

$ pwd
/media/knoppix//squid3/4.15

$ ls -l
total 0
drwxrwxrwx 1 root root 0 May 29 03:16 bin
drwxrwxrwx 1 root root 0 May 29 03:14 etc
drwxrwxrwx 1 root root 0 May 29 03:16 sbin
drwxrwxrwx 1 root root 0 May 29 03:16 share
drwxrwxrwx 1 root root 0 May 29 03:16 var
$

 so what could the problem be? Why doesn't squid look into the path I
defined as prefix?

 lbrtchx